From: NTB Technical Support <techsupport@ntb.org.uk>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: ADO and ODBC: More
Date: Thu, 5 Jul 2001 18:29:31 +0100
Message-ID: <004301c10578$0d4dc720$2780bcc3@northeast.co.uk> (raw)
References: <000d01c1056a$00dadc20$2780bcc3@northeast.co.uk>
<3419.994351105@sss.pgh.pa.us>
> 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!
> I don't like the idea of changing what SQLColAttributes returns ...
> that seems certain to break other applications.
That was, my guess too.
> But first, a wild stab in the dark --- what happens if you write
> RS("""child beds""") = 33
> ie provide the quotes at the application level?
Ah. Well. The recordset is a "collection" (like an associative array) whose
contents is created by ADO from the field names of the most-recently
executed query - so """child beds""" would be a non-existent member of the
collection...
Tim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: techsupport@ntb.org.uk, tgl@sss.pgh.pa.us
Subject: Re: ADO and ODBC: More
In-Reply-To: <004301c10578$0d4dc720$2780bcc3@northeast.co.uk>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox