Re: psqlODBC ODBC3.0/Column Names

> -----Original Message-----
> From: Hiroshi Inoue [mailto:Inoue(at)tpf(dot)co(dot)jp]
> Sent: 28 March 2002 13:45
> To: Dave Page
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] psqlODBC ODBC3.0/Column Names
>
>
> > -----Original Message-----
> > From: Dave Page [mailto:dpage(at)vale-housing(dot)co(dot)uk]
> > >
> > > > Attached. This represents a complete run of the program
> > > using the v3
> > > > driver. I have changed the references to the column names in the
> > > > program to Column1 etc. just to stop it erroring.
> > >
> > > You seem to be forgetting to call DataAdapter.Update method.
> >
> > Yes, thanks. Unfortunately though, both my problems remain.
> >
> > - The ODBC3 driver returns 'Column1','Column2' etc as the column
> > names (the
> > 2.5 driver is fine).
>
> Hmm I see neither here.
> Please try the latest driver at
> http://w2422.nsk.ne.jp/~inoue/ . No explicit
> OdbcCommandBuilder is needed.

Aha. The unicode enabled v3 driver is returning the column names correctly.
Thanks.

I'm still not getting update/insert/delete commands though, either with or
without the OdbcCommandBuilder. I must admit confused by you saying I don't
need it though, I thought the whole point was that the DataAdaptor *didn't*
spend time figuring out the queries & their parameters unless explicitly
told to (from the Microsoft docs):

The OdbcDataAdapter does not automatically generate the SQL statements
required to reconcile changes made to a DataSet associated with the data
source. However, you can create an OdbcCommandBuilder object that generates
SQL statements for single-table updates by setting the SelectCommand
property of the OdbcDataAdapter. Then, the OdbcCommandBuilder generates any
additional SQL statements that you do not set.

Regards, Dave.