[postgis-devel] Exceptions vs. WARNINGS from GEOS functions
strk
strk at keybit.net
Sat Feb 20 11:36:20 PST 2010
On Sat, Feb 20, 2010 at 11:20:06AM -0800, Paul Ramsey wrote:
> Quietly screwing up seems very dangerous to me...
Uhm... would be a NULL return.
It means "I dunno", in sql terms.
And usually it's viral (if lower-level functions do not know higher
level ones will inherit that ignorance with the NULL bubbling up to
final user).
Maybe it needs more research on the "maybe" part ?
--strk;
>
> On Sat, Feb 20, 2010 at 10:46 AM, strk <strk at keybit.net> wrote:
> > What do you think about changing all GEOS wrappers
> > so they elog(WARNING) and return NULL rather than
> > elog(ERROR) and thus break transactions ?
> >
> > Easy vote & go ?
> >
> > --strk;
> >
> > () Free GIS & Flash consultant/developer
> > /\ http://foo.keybit.net/~strk/services.html
> > _______________________________________________
> > postgis-devel mailing list
> > postgis-devel at postgis.refractions.net
> > http://postgis.refractions.net/mailman/listinfo/postgis-devel
> >
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
--
() Free GIS & Flash consultant/developer
/\ http://foo.keybit.net/~strk/services.html
More information about the postgis-devel
mailing list