To: "NTB Technical Support" <techsupport@ntb.org.uk>
cc: pgsql-interfaces@postgresql.org
Subject: Re: ADO and ODBC: More 
In-reply-to: <000d01c1056a$00dadc20$2780bcc3@northeast.co.uk> 
References: <000d01c1056a$00dadc20$2780bcc3@northeast.co.uk>
Comments: In-reply-to "NTB Technical Support" <techsupport@ntb.org.uk>
	message dated "Thu, 05 Jul 2001 16:48:57 +0100"
Date: Thu, 05 Jul 2001 12:38:25 -0400
Message-ID: <3419.994351105@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

"NTB Technical Support" <techsupport@ntb.org.uk> writes:
> I basically don't know anything about ODBC, but it looks to me like
> ADO/OLEDB is either getting misled about whether it needs to quote the
> column name containing spaces, or it is just not doing it right.

Curious that it quotes the table name (which doesn't need it) and then
doesn't quote the column name (which does).  Since SQLColAttributes
isn't returning a pre-quoted table name, clearly ADO has heard of the
idea that it ought to quote names.  It's just omitting to do it for
the column name.

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 don't like the idea of changing what SQLColAttributes returns ...
that seems certain to break other applications.

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?

			regards, tom lane