Damn right man - thanks! On Saturday, November 1, 2014, Sandro Santilli <[email protected]> wrote:
> On Fri, Oct 31, 2014 at 05:12:40PM -0400, Robert Burgholzer wrote: > > So just for accuracy, I was incorrect, sort of. While the functions > that I > > am currently using "contains, within, ..." will do the CAST implicitly, > the > > GIST index does not like the bytea type. Which makes the adoption of an > > actual geometry column even more urgent. > > For further accuracy, you might pass the GiST index an expression, then > it'll like it. Example: > > create index on mytable using gist (geometry(mybytea)); > explain select gid from mytable where mybytea && ST_MakeEnvelope(0,0,1,1); > > --strk; > _______________________________________________ > postgis-users mailing list > [email protected] <javascript:;> > http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users > -- -- Robert W. Burgholzer 'Making the simple complicated is commonplace; making the complicated simple, awesomely simple, that's creativity.' - Charles Mingus Athletics: http://athleticalgorithm.wordpress.com/ Science: http://robertwb.wordpress.com/ Wine: http://reesvineyard.wordpress.com/
_______________________________________________ postgis-users mailing list [email protected] http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
