[postgis-devel] Re: Search Path and Function Overloading

[strk at refractions.net]

On Mon, Mar 05, 2007 at 01:16:30PM +0000, Mark Cave-Ayland wrote:
> On Fri, 2007-03-02 at 10:33 -0800, Paul Ramsey wrote:
> > Paolo,
> > 
> > This is perhaps best discussed on postgis-devel. I do not know that 
> > there is any good/easy answer. I would like to most all our functions to 
> > st_* space at some point, but that is a huge backward-compatible break, 
> > and if we leave in backwards-compatible hooks, your problem remains.
> > 
> > P
> 
> Perhaps the best action would be to require the cast from PostgreSQL
> geometries to be explicit rather than implicit? See

Yes, I think it should not be implicit.
line 2783 of lwpostgis.sql.in needs be changed.

CREATE CAST (geometry AS box) WITH FUNCTION box(geometry) AS IMPLICIT;

--strk;