Re: A Small psql Suggestion - Mailing list pgsql-general

From Adrian Klaver
Subject Re: A Small psql Suggestion
Date
Msg-id fe011f81-4c5f-b5d5-eaf9-d2203b18debc@aklaver.com
Whole thread Raw
In response to Re: A Small psql Suggestion  (Brad White <b55white@gmail.com>)
Responses Re: A Small psql Suggestion  (Brad White <b55white@gmail.com>)
List pgsql-general
On 2/7/23 16:00, Brad White wrote:
> 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 "Order 
> Items" does not exist at character 35
> 
> Any suggestions on where to look?

1) Do not tack on to an existing thread, create a new post.

2) Where is the query coming from, manually created code or something 
ORM like?

3)
> 
> Thanks,
> Brad.

-- 
Adrian Klaver
adrian.klaver@aklaver.com




pgsql-general by date:

Previous
From: Brad White
Date:
Subject: Re: A Small psql Suggestion
Next
From: Brad White
Date:
Subject: Quoting issue from ODBC