The solution seems to be to define NOT NULL columns as DEFAULT NULL. This way
the application logic is not broken and at the same time GeoServer doesn't
register the layer as readonly (as it sees the DEFAULT clause).

--
View this message in context: 
http://osgeo-org.1803224.n2.nabble.com/Readonly-WFS-layer-tp6848399p6850010.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to