[Gdal-dev] OGR OLEDB Provider

[Tamas Szekeres]

Frank,

I understand your concerns. So far I didn't realize that this driver
exists in the trunk at all. So it would take me a while to see whether
it's worthy to keep or not from the aspect of the
usability/performance.
However I'm not really aware of the necessary steps from the aspect of
the provenance. If it would require the corresponding code to be
rewritten then it wouldn't be so realistic to keep that in.


Best regards,

Tamas


2007/9/12, Frank Warmerdam <warmerdam at pobox.com>:
> Tamas Szekeres wrote:
> > Frank,
> >
> > Although I didn't play much with this implementation I would
> > discourage to omit that officially without any compelling reasons. I
> > thinks the (native) OLEDB interface has a faily large audience
> > comparing with the ODBC interface from the aspect of the MS SQL server
> > for years. I can guess it provides a performance impact as well, so I
> > think we should do some examination before taking this step.
>
> Tamas,
>
> I would stress that this is not a replacement for OGR's ability to
> access ODBC datasources since it is on "the other side".  That is it
> provides an OLE DB interface to OGR.  There is currently no comparible
> ODBC interface to OGR.
>
> Would you be willing to address the code provenance concerns with the
> OLE DB provider?  If they can be resolved, I'd be fine with keeping
> the OLE DB provider in trunk.
>
>    http://trac.osgeo.org/gdal/ticket/1817
>
> Best regards,
> --
> ---------------------------------------+--------------------------------------
> I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
> light and sound - activate the windows | http://pobox.com/~warmerdam
> and watch the world go round - Rush    | President OSGeo, http://osgeo.org
>
>