Re: Exception handling the correct way

The postgres log is where I look for details on errors Jakob søn. 10. mar. 2024 14.55 skrev Michal Seidl : > Hello, > is there any standard way how to catch Exceptions from Postgis functions? > > For Example: > SELECT ST_Split(polygon_geom, polygon_geom) > > result in general PostgreSQL

Re: Exception handling the correct way

Hello, may be I did not say it clearly enough. I mean how to catch from programing language code. PHP, Python, ... To look in log is not the right way I guess. Michal On 3/10/24 16:01, 5P0CK wrote: The postgres log is where I look for details on errors Jakob søn. 10. mar. 2024 14.55 skrev

Exception handling the correct way

Hello, is there any standard way how to catch Exceptions from Postgis functions? For Example: SELECT ST_Split(polygon_geom, polygon_geom) result in general PostgreSQL InternalError exception with CODE XX000. This is not very helpful to catch such specific error. It seem to me that also any

Error when parsing GML with st_geomfromgml

Hello, I get an error when trying to parse GML data with ST-GeomFromGML(). I have this GML data and PostGis version POSTGIS="3.3.6 cfe89b3" [EXTENSION] PGSQL="150" GEOS="3.12.1-CAPI-1.18.1" PROJ="9.0.1" LIBXML="2.9.7" LIBJSON="0.13.1" LIBPROTOBUF="1.3.0" WAGYU="0.5.0 (Internal)" (core procs from

Re: Exception handling the correct way

> > is there any standard way how to catch Exceptions from Postgis functions? > For Example: > SELECT ST_Split(polygon_geom, polygon_geom) > result in general PostgreSQL InternalError exception with CODE XX000. > My preferred way is to write a custom wrapper function in PL/pgSQL for error

RE: Error when parsing GML with st_geomfromgml

You are missing double-quotes, on the xmlns schemes, but even putting those in, I still get an ERROR: invalid GML representation I haven't tried ST_GeomFromGML with curved geometries before or added namespaces, so it's possible curves are not supported since there is no mention on the page