[Mapserver-west] postgis query size limit

[Tyler Mitchell]

I'm not familiar with this problem, but I wonder about a couple of things:
-Are you really using the WHERE key=value1 OR key=value2..?  Won't
WHERE key IN (value1, value2, value3)
do it for you?  It will at least keep the query shorter and that might help 
you!?

Hope you find an answer!
Tyler

On May 12, 2005 04:17 pm, Ken-ichi wrote:
> Hi all.  I've been having trouble using very long PostGIS queries within
> MapServer.  I found this year-old email on the same topic
>
> http://lists.gis.umn.edu/pipermail/mapserver-users/2004-February/010233.htm
>l
>
> and I was wondering if anyone knows if this problem has been fixed.
>
> My situation is as follows: I'm in an awkward bind in which all the
> non-spatial parts of a dataset reside in a MySQL database, and all the
> spatial stuff is in PostGIS.  When a user queries the MySQL db, they get
> back a bunch of unique record identifiers that can then be used to pull
> point data out of the PostGIS table by setting a really long WHERE
> clause (ie 'WHERE key=value1 OR key=value2 OR key=value3, etc).  All
> well and good, until I start trying to pull out more than about 400
> records.  Then MapServer chokes and I get a 500 error.
>
> If anyone can think of a better way around this problem, I'm all ears.
> Thanks.
>
> -Ken-ichi
>
> PS.  Anyone going to Open Source Geospatial '05?  I just registered.
> _______________________________________________
> Mapserver-west mailing list
> Mapserver-west at lists.maptools.org
> http://lists.maptools.org/mailman/listinfo/mapserver-west