[gdal-dev] Ingres driver for gdal

[Even Rouault]

For the seg fault, I've taken the liberty to fix it myself (r15463) as the fix 
was obvious. But I encourage you - and others - to query the trac ticket 
system (http://trac.osgeo.org/gdal/report/1?sort=ticket&asc=0) and create new 
tickets if needed so that bug reports and patches don't get lost in the email 
flow (http://trac.osgeo.org/gdal/newticket)

For the questions, I can't answer. The revision log shows that Frank Warmerdam 
is probably the right man for that ;-)

Best regards.

Even

Le Monday 06 October 2008 17:11:31 Denise MacLeod, vous avez écrit :
> Hi -
>
> I am another recent addition to the GDAL community. I am currently using
> the Ingres driver for the latest svn trunk version. I had originally
> downloaded the driver back in May, and had it working, but the latest
> version wasn't working for me; specifically ogr2ogr was seg faulting.
>
> After some digging, I found out that the command line syntax had changed
> between May and now.  Previously, this syntax worked:
>
>    ogr2ogr -overwrite -append -skipfailures -f ingres INGRES:mydbname
> road.shp
>
> Now however, the syntax is (as documented on the GDAL website):
>
>    ogr2ogr -overwrite -append -skipfailues -f Ingres
> "@driver=ingres,dbname=mydbname,user=mydbuser,password=mypwd" road.shp
>
> I was wondering if there's a reason to have the syntax so different from
> some of the other formats, such as Postgres?  (with the @ sign at the
> beginning). Also, out of curiousity, is the new driver parameter used to
> separate the vector format (specified by "-f Ingres") from the driver used?
>
> Finally, I fixed the seg fault by initializing the data source pointer as
> such:
>
> from ogr/ogrsf_frmts/ingres/ogringresdriver.cpp
>
>   OGRDataSource *OGRIngresDriver::CreateDataSource( const char * pszName,
>                                                     char ** /* papszOptions
> */ )
>
>   {
>
> >     OGRIngresDataSource     *poDS = NULL;
>
> .....
>
> Thanks,
> Denise