You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 6, 2021. It is now read-only.
Hi, we've been using FeatureServer for a while and we just jumped from 1.12 to 1.15.2.
We use it exclusively with Postgis and we've found out some problems using schema and case sensitive columns. Plus we where not able to have a good response after an action other than select.
So I brewed up a patch, but I need your help a little. I'd like to write Tests for it so it would not break anymore, but I don't really know where to start. I'm not even able to run those alerady present.
And I'd like to know the Idea arround the actionTransactions, since it's only in postGIS and that it's broken I've set the response back to the logic before that (the select of the element).
Hi, we've been using FeatureServer for a while and we just jumped from 1.12 to 1.15.2.
We use it exclusively with Postgis and we've found out some problems using schema and case sensitive columns. Plus we where not able to have a good response after an action other than select.
So I brewed up a patch, but I need your help a little. I'd like to write Tests for it so it would not break anymore, but I don't really know where to start. I'm not even able to run those alerady present.
And I'd like to know the Idea arround the actionTransactions, since it's only in postGIS and that it's broken I've set the response back to the logic before that (the select of the element).
Here's a link to what I've done :
https://github.com/solution-globale-informatique/featureserver/tree/CaseSensitivePostGis
Once the tests are done I'll do a pull request.
Thanks for all you've done!
The text was updated successfully, but these errors were encountered: