About Mapserver Native Oracle support and OGR Oracle support

[Robert oude Lohuis]

True, but there is a difference:

The native support does not have the capability to get administrative data
from the database, but delivers only the geometry data. OGR does have
support for queries which deliver data of other database-columns other than
the geometry column.

But, as Bart already mentioned, this comes with a price. The performance
decreased in our case with a factor 2.

greetz,

Robert.

On Mon, 24 Oct 2005 12:05:25 +0200, Bart van den Eijnden
<BEN at SYNCERA-ITSOLUTIONS.NL> wrote:

>I think the Mapserver native would be the preferred way. It should have the
best performance, and it has the same features as the OGR one. Note that the
OGR OCI driver was mostly developed for writing data and not so much for
reading (so it might not be completely optimized for that).
>
>Best regards,
>Bart
>
>Bart van den Eijnden
>Syncera IT Solutions
>Postbus 270
>2600 AG  DELFT
>
>tel.nr.: 015-7512436
>email: BEN at Syncera-ITSolutions.nl
>
>>>> Jukka Sirviö <Jukka.Sirvio at ARBONAUT.COM> 24-10-2005 10:24 >>>
>Hello!
>Does anyone have a suggestion which is the preferred way for getting the
>spatial data from Oracle? Is it Mapserver Native support or is it through
>OGR / gdal? What are the drawbacks / benefits for both of these? I already
>know that if I use ogr approach I have to compile gdal and then compile
>mapserver for this version of gdal.
>
>I quess that Mapserver native approach is more widely used?
>
>
>Yours:
>Jukka