From: | Brad White <b55white(at)gmail(dot)com> |
---|---|
To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Quoting issue from ODBC |
Date: | 2023-02-08 00:10:44 |
Message-ID: | CAA_1=93z4oEXKQ9GHtDkEQhEe5r39C8YSDMpwO8OHmSBreXw3g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-odbc |
Front end: Access 365
Back end: Postgres 9.4
(I know, we are in the process of upgrading)
I'm getting some cases where the SQL sent from MS-Access is failing.
Looking at the postgres log shows that the field names and table names are
not being quoted properly.
It has been my experience that Access usually does a better job at
converting the queries than I would have expected, but not in this instance.
For example
Access: connection.Execute "UPDATE [" & strTable & "] SET [" & strTable &
"].[InsertFlag] = Null" _
& " WHERE ((([" & strTable & "].[InsertFlag])=" & lngCurrUID & "));", ,
adCmdText Or adExecuteNoRecords
Note that InsertFlag is bracketed the same way in both instances.
PSQL: UPDATE "public"."Orders" SET InsertFlag=NULL WHERE ("InsertFlag" =
166 )
Note that InsertFlag is quoted once but not the other time.
Of course this gives the error: column "insertflag" of relation "Orders"
does not exist at character 35.
Looks like I have about 16 unique instances of statements not being quoted
correctly resulting in over 500 errors in the log for today.
Any suggestions on where to look?
Thanks,
Brad.
From | Date | Subject | |
---|---|---|---|
Next Message | Brad White | 2023-02-08 00:11:49 | Re: PostgreSQL |
Previous Message | Adrian Klaver | 2023-02-08 00:05:44 | Re: A Small psql Suggestion |
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2023-02-08 00:19:08 | Re: Quoting issue from ODBC |
Previous Message | Clemens Ladisch | 2023-02-07 18:45:49 | Re: psqlODBC development and support |