[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgis-devel
Subject:    [postgis-devel] Re: pgsql 7.3
From:       redmonde () purdue ! edu
Date:       2002-08-19 20:19:48
Message-ID: 1029788388.3d6152e4b4f74 () webmail ! purdue ! edu
[Download RAW message or body]

> Doing "...WHERE geom && 'BOX3D(2 2 0,3 3 0)'::box3d" will create a
> BOX3D
> object, then convert this BOX3D object to a GEOMETRY without any real
> geometry (exactly like above).  This convesion is automagically
> detected
> by postgresql - postgresql will see a function that takes a GEOMETRY
> as
> an argument, but is actually given a BOX3D.  It will then look for a
> function that converts a BOX3D into a GEOMETRY.  Imagine this 'smarts'
> has been dumbed down in 7.3 to clear up some other issues.
> 
> I think I've fixed the postgis.sql.in file for 7.3 - the work around
> for
> these problems is to just explictly replace '::box3d' with
> '::geometry'.  I'll try to find out what the postgresql developers
> have
> done - was there anything in the README?
> 
> dave

Actually, "SELECT * from geom_test WHERE geom && 'BOX3D(2 2 0,3 3 0)'::box3d;" was \
from the README. Replacing 'box3d' with 'geometry' was what I had done as well. I \
stopped persuing that issue because I was hoping that it will later be fixed. Tom \
Lane responded that the error was indeed a bug with someone's patch, so hopefully \
casting should still work the same in the future.

Eric


[prev in list] [next in list] [prev in thread] [next in thread]