Message-ID: <3B450464.8E52CA70@tpf.co.jp>
Date: Fri, 06 Jul 2001 09:20:52 +0900
From: Hiroshi Inoue <Inoue@tpf.co.jp>
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: NTB Technical Support <techsupport@ntb.org.uk>,
	pgsql-interfaces@postgresql.org
Subject: Re: ADO and ODBC: More
References: <000d01c1056a$00dadc20$2780bcc3@northeast.co.uk>
	<3419.994351105@sss.pgh.pa.us>
	<004301c10578$0d4dc720$2780bcc3@northeast.co.uk>
	<3779.994357122@sss.pgh.pa.us>
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit

Tom Lane wrote:
> 
> "NTB Technical Support" <techsupport@ntb.org.uk> writes:
> >> I'd write it off as broken code in ADO, and program around it by not
> >> using column names that require quoting.  Ugly answer, but it's not
> >> clear that you have an alternative (short of waiting for an ADO fix).
> 
> > I just don't fancy modifying all those hundreds of pages of
> > code... And it works with SQL Server, so that would have to be broken
> > in a compatible fashion!
> 
> It does eh?  Hmm, that suggests that there is *some* way to make the
> right thing happen.  Anyone know how Microsoft's version of
> SQLColAttributes acts with such names?
> 

ADO doesn't need ODBC essentially and M$ SQL Server has
its own OLE DB provider. PostgreSQL doesn't have its OLE
DB provider implementation yet and has to use M$ OLD DB 
provider for ODBC.
I don't know why the table name is quoted but the column
names aren't. There are many applications which quote
column/table names properly(unconditionally?). So it seems
very hard to change SQLxxxx.
Another way is to implement driver cursors. Actually I plan
to implement static/keyset-driven cursors. However I'm not
sure I can do it and couldn't guarantee when it is ready.

regards,
Hiroshi Inoue