Maybe it would be better to check postgres logs to get that kind of info.
I don't recall getting any database specific eror messages in geoserver
log/responses...

Richard Duivenvoorde <rdmaili...@duif.net> escreveu no dia quinta,
28/05/2020 à(s) 07:31:

> Hi,
>
> If you raise the log file level (via the admin interface
> Settings/Global/Logging Settings one of the developer or verbose
> settings will show you queries and responses of the database.
>
> You can see the logs on your server, OR in the admin interface in
> About&Status/Geoserver Logs.
>
> Hope this helps,
>
> Regards,
> Richard Duivenvoorde
> On 5/27/20 9:34 PM, fibizzo wrote:
> > I have deployed geoserver 2.14.5 in Wildfly 11
> >
> > My geoserver layers are connected to a postgres database with postgis; in
> > postgis I added certain constraints about inserting new records, i.e. two
> > polygons cannot touch each other/cannot contain another polygon
> >
> > In a POST request of inserting or updating, how can I get the constraint
> > errors? with a WFS insert request, I just get this message:
> >
> > <ows:ExceptionReport xmlns:xs="http://www.w3.org/2001/XMLSchema";
> > xmlns:ows="http://www.opengis.net/ows";
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; version="1.0.0"
> > xsi:schemaLocation="http://www.opengis.net/ows
> > http://myserver:8080/geoserver/schemas/ows/1.0.0/owsExceptionReport.xsd
> ">
> >     <ows:Exception exceptionCode="InvalidParameterValue">
> >         <ows:ExceptionText>Update error: Error occured updating
> > features</ows:ExceptionText>
> >     </ows:Exception>
> > </ows:ExceptionReport>
> >
> > I can get the entire stacktrace in geoserver and make sure what
> constraint
> > was triggered, is there a way to obtain more detail in my response?
> >
> >
> >
> >
> > --
> > Sent from:
> http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html
> >
> >
> > _______________________________________________
> > Geoserver-users mailing list
> >
> > Please make sure you read the following two resources before posting to
> this list:
> > - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> > - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
> >
> > If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
> >
> >
> > Geoserver-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/geoserver-users
> >
>
>
>
> _______________________________________________
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>


-- 

www.vfonsecaz.pt
_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to