Hi Mauro Problably there is a kind of mapserver bug. As far as I know maspserver-oracle supports a maximum of 6000 chars for SQL-statement and the code doesn't handle overflow's gracefully.
On the other hand: Even if mapserver could handle SQL-strings of arbitrary length, you still have to deal with the Oracle-Limit of 1000 elements in the "CODE IN (...)"-Expression. (http://download-uk.oracle.com/docs/cd/A87861_01/NT817EE/server.817/a85397/expressi.htm#1029285) Maybe you are forced to look for a different approach anyway? By Benedikt Rothe UMN MapServer Users List <[email protected]> schrieb am 11.10.2007 19:48:36: > Hi list > > I am using mapserver 5.0 with java mapscript. > I use oracle spatial 10g. > I have problems with long string (longer then 2k) > used to specify complex data sql connection query or filter. > When mapscript execute for instance setFilter it crashes. > I suspect there is a general issue with long string. > The same string used directly in the mapfile works correctly. > It is probably a mapscript memory allocation problem. > While I can use an oracle view to avoide the problem for the > connection query, I do not know how to avoide it with the filter, > because it is known only at run time. > The filter can be something like: > CODE IN ('1','2','3'....very long string ... '1000') > > Can this be set as a bug? > > Thank you for any suggestion > > Mauro Sartori > > > > ------------------------------------------------------ > Leggi GRATIS le tue mail con il telefonino i-mode? di Wind > http://i-mode.wind.it/ >
