some of our clients have come up with a few quirks in the native oracle driver that should be taken into account:
* the strings storing the fields returned by the database have a fixed length in mapserver, so that might have to be overridden at compile time if you are planning to return data longer than a certain value (2048 bytes from memory). For normal map rendering this shouldn't be a problem, but problems may arise when doing wfs queries and returning a paragraph of text for example in an attribute. * I haven't investigated this much more, but we've also had problems with long query strings (we're talking DATA mapfile strings of several kbytes here) regards, thomas www.camptocamp.com +33 4 79 26 57 97 On Fri, Jul 10, 2009 at 17:59, Schlagel, Joel D IWR<joel.d.schla...@usace.army.mil> wrote: > For what it's worth - we've used the oracle direct connect in a production > environment all day, every day for several years with no quirks to report. > > -joel > > > > On 7/10/09 11:36 AM, "Frank Warmerdam" <warmer...@pobox.com> wrote: > >> YOUNESS ELMEDRAOUI wrote: >>> Hello everybody, >>> >>> i have a question: >>> what's the difference between a connection to oracle DB with native >>> oraclespatial and OGR? >>> performance, ...?? >> >> Youness, >> >> Generally speaking the direct connection should be faster since it avoids >> a lot of OGR overhead. They are completely distict implementations so >> you might find each has quirks and strengths though I can't really identify >> them off hand. >> >> Best regards, > > > -joel > > -- > Joel D. Schlagel > US Army Engineer Institute for Water Resources > http://www.iwr.usace.army.mil > > > _______________________________________________ > mapserver-users mailing list > mapserver-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/mapserver-users > _______________________________________________ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users