Обсуждение: Re: Bug#108286: case sensitivity in column names
"Oliver Elphick" <olly@lfix.co.uk> writes:
> You must have created the table in PostgreSQL using quoted names for
> the column (but not for the table, since PostgreSQL matches
> FaultAttributes with faultattributes).
Yep.
> Why not dump and recreate your database, but edit the dumpfile to
> remove the double-quotes and thus force the names to become
> case-insensitive? Then it won't matter that OleDB is sending garbage.
I've tried to pass double quotes through OleDB, but it doesn't seem to
work. On the other hand, double quotes do work with SQL
statements through (I assume) ODBC.
So to sum up,
recreated database without quotes (changing a few names that
clashed),
and
changing direct SQL queries to not quote names
did the trick (mostly).
What remains of the wishlist item is, I guess, a wish for a case sensitive
OleDB driver. Thanks for your help in clarifying things!
-kzm
--
If I haven't seen further, it is by standing in the footprints of giants
Did someone say OLE DB? As I remember, there are quite a few people looking for this. Or was it a _native_ OLE DB driver? -Cedar > "Oliver Elphick" <olly@lfix.co.uk> writes: > > > Why not dump and recreate your database, but edit the dumpfile to > > remove the double-quotes and thus force the names to become > > case-insensitive? Then it won't matter that OleDB is sending garbage. ...
Cedar Cox <cedarc@visionforisrael.com> writes: > Did someone say OLE DB? As I remember, there are quite a few people > looking for this. Or was it a _native_ OLE DB driver? I'm not an expert on Microsoft's rather confusing conglomerate of database access APIs, but as I understand it (from our resident professional), our application accesses its database through OLEDB. The steps I used were: 1> installed the PostgreSQL ODBC driver, available from you-know-where. 2> brought up the control panel, and added my PostgreSQL database as a (system, I think) data source. 3> in the application's database selection, picked the driver for ODBC sources. Still have some problems, but at least we can read and write the database tables. -kzm -- If I haven't seen further, it is by standing in the footprints of giants
If your using VB6, and ADO, then the layers are as follows: ADO | OLEDB (specifically "ODBC by OLDB" driver) | ODBC | PostgreSQL > -----Original Message----- > From: pgsql-odbc-owner@postgresql.org > [mailto:pgsql-odbc-owner@postgresql.org]On Behalf Of Ketil Malde > Sent: Monday, 13 August 2001 4:32 PM > To: Cedar Cox > Cc: pgsql-odbc@postgresql.org > Subject: Re: [ODBC] Re: Bug#108286: case sensitivity in column names > > > Cedar Cox <cedarc@visionforisrael.com> writes: > > > Did someone say OLE DB? As I remember, there are quite a few people > > looking for this. Or was it a _native_ OLE DB driver? > > I'm not an expert on Microsoft's rather confusing conglomerate of > database access APIs, but as I understand it (from our resident > professional), our application accesses its database through OLEDB. > > The steps I used were: > 1> installed the PostgreSQL ODBC driver, available from > you-know-where. > 2> brought up the control panel, and added my PostgreSQL database as a > (system, I think) data source. > 3> in the application's database selection, picked the driver for ODBC > sources. > > Still have some problems, but at least we can read and write the > database tables. > > -kzm > -- > If I haven't seen further, it is by standing in the footprints of giants > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/users-lounge/docs/faq.html