From: Thomas Lockhart <lockhart@alumni.caltech.edu>
To: Cedar Cox <cedarc@visionforisrael.com>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: textcat() and ODBC driver
Date: Wed, 27 Dec 2000 16:38:29 +0000
Message-ID: <3A4A1B05.7D0B1140@alumni.caltech.edu> (raw)
References: <Pine.LNX.4.21.0012271117370.19237-100000@nanu.visionforisrael.com>
> The response I got was that the odbc code is not smart enough to nest
> textcat functions. A recent discovery ;) brings me to this question, Why
> is textcat being used? Why not just use the || operator? Unless there's
> something I don't know it seems to be a direct replacement for the &
> operator in Access/VB. Thoughts? Someone willing to change it?
There *may* be some translation in the ODBC driver to get from an ODBC
function call to textcat() (I haven't looked at it since last spring).
But I'm pretty sure that there is no "operator mapping" in the driver,
and that Access itself is converting from the (nonstandard) ampersand to
some function call. Have you tried forming the query with the SQL92 "||"
operator? Or is this some automatic query from Access which you cannot,
uh, access?
- Thomas
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: lockhart@alumni.caltech.edu, cedarc@visionforisrael.com
Subject: Re: textcat() and ODBC driver
In-Reply-To: <3A4A1B05.7D0B1140@alumni.caltech.edu>
* 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