pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedPSQLODBC and TRANSACTIONS
2+ messages / 2 participants
[nested] [flat]
* PSQLODBC and TRANSACTIONS
@ 1999-01-12 09:55 Jose' Soares <jose@sferacarta.com>
1999-01-12 15:55 ` Re: [INTERFACES] PSQLODBC and TRANSACTIONS Byron Nikolaidis <byronn@insightdist.com>
0 siblings, 1 reply; 2+ messages in thread
From: Jose' Soares @ 1999-01-12 09:55 UTC (permalink / raw)
To: pgsql-interfaces
Hi,
I'm trying transactions using M$-access and PSQLODBC without success,
Seems that backend locks itself
by opening two connections to work on the same table.
I have a table with 3 rows:
codice nome cap
---------------------------
1 pippo 0
2 pluto 0
3 topolino 0
---------------------------
I tryed to update table as:
UPDATE operatori SET cap = 1;
This works, but the next...
UPDATE operatori SET cap = 2;
At this point the backend was locked and I had to break connection...
(See attached log file)
Thanks for any help.
-Jose'-
Attachments:
psqlodbc_4294795803.log (application/x-unknown-content-type-log_auto_file, 4.9K) download
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: [INTERFACES] PSQLODBC and TRANSACTIONS
1999-01-12 09:55 PSQLODBC and TRANSACTIONS Jose' Soares <jose@sferacarta.com>
@ 1999-01-12 15:55 ` Byron Nikolaidis <byronn@insightdist.com>
0 siblings, 0 replies; 2+ messages in thread
From: Byron Nikolaidis @ 1999-01-12 15:55 UTC (permalink / raw)
To: sferac@bo.nettuno.it; +Cc: pgsql-interfaces
Jose' Soares wrote:
> Hi,
>
> I'm trying transactions using M$-access and PSQLODBC without success,
> Seems that backend locks itself
> by opening two connections to work on the same table.
>
> I have a table with 3 rows:
>
> codice nome cap
> ---------------------------
> 1 pippo 0
> 2 pluto 0
> 3 topolino 0
> ---------------------------
>
The logfile shows that Access is using Manual Commit. The last two lines show a separate connection
being made and then a select statement on "operatori" table. But it is still locked from the other
connection. (see below)
I don't think there is anything the driver can do about this. You need Vladim's new locking code! I
think that is going to be in the next version of Postgres.
Byron
<Highlights from the logfile>
BEGIN
UPDATE "operatori" SET "cap"='1' WHERE "codice" = '1 '
SELECT "codice","cap" FROM "operatori" WHERE "codice" = '3 '
UPDATE "operatori" SET "cap"='1' WHERE "codice" = '3 '
SELECT "codice","cap" FROM "operatori" WHERE "codice" = '2 '
UPDATE "operatori" SET "cap"='1' WHERE "codice" = '2 '
<Another connection is created here>
SQLDriverConnect(out)='DSN=PostgreSQL;DATABASE=hygea;SERVER=verde;PORT=5432;UID=marco;PWD=;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=0;CONNSETTINGS=set+ksqo+to+%27on%27%3b'
<This one hangs it>
SELECT "operatori"."codice" FROM "operatori"
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~1999-01-12 15:55 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-01-12 09:55 PSQLODBC and TRANSACTIONS Jose' Soares <jose@sferacarta.com>
1999-01-12 15:55 ` Byron Nikolaidis <byronn@insightdist.com>
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