From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Boylan, Ross" <Ross(dot)Boylan(at)ucsf(dot)edu> |
Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Semi-unable to add new records to table--primary key needed? |
Date: | 2019-12-21 03:06:18 |
Message-ID: | 10211.1576897578@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Boylan, Ross" <Ross(dot)Boylan(at)ucsf(dot)edu> writes:
> I have a table that seems to act for some purposes as if I can't add new records to it. I would like to understand why that is and fix it.
> The initial problem was that an MS-Access application using an ODBC driver (driver and database 64 bit PG 12.0) failed at
> DoCmd.GoToRecord , , acNewRec
> which is basically saying to create a new record in the table. The error was something like unable to create record. Unfortunately DoCmd is a black box; I can only speculate what it is doing.
Aren't black-box apps fun? You might get some insight from looking into
the postmaster log to see what error the database thinks it's throwing.
Perhaps also turn on "log_statement = all" to record full details of
what SQL commands the app is sending.
Also, as I recall, the pgsql-odbc driver has some ability to do client-side
query tracing. I'm not familiar with the details of that though.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2019-12-21 05:02:42 | Re: Semi-unable to add new records to table--primary key needed? |
Previous Message | Ron | 2019-12-21 02:28:01 | Re: Semi-unable to add new records to table--primary key needed? |