Skip site navigation (1) Skip section navigation (2)

Re: Record locking issue using ODBC from .NET

From: Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp>
To: anomatos(at)freemail(dot)gr
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Record locking issue using ODBC from .NET
Date: 2006-08-29 23:39:27
Message-ID: 44F4D02F.3080406@tpf.co.jp (view raw or flat)
Thread:
Lists: pgsql-odbc
Hi Antonis,
Which version of driver are you using ?

regards,
Hiroshi Inoue

anomatos(at)freemail(dot)gr wrote:
> I want to have exclusive read access to a table row, so that if a client has access to that row, any other client should either wait or get an error of the type "could not obtain lock on row in relation 'customers'", depending on the semantics used in the query string(nowait)
> 
> Both clients execute:
> 
> ...
> OdbcTransaction ^ transaction = connection->BeginTransaction();
> String ^ query = "select * from customers where id = 3 for update nowait";
> OdbcCommand ^ cmd = (gcnew OdbcCommand(query, connection, transaction));
> reader = cmd->ExecuteReader();
> ...
> 
> After the first client locks the record and before he ends the transaction, the second tries to acquire the lock. As expected an exception is raised, BUT:
> 
> One would expect that this exception is of type OdbcException explaining that "the lock cannot be aquired". Instead of this I get a System::InvalidOperationException which disables my connection for some reason. However the above exception hosts an inner exception of the desired type(OdbcException). 
> 
> Does anybody have any idea why I get this type of behaviour, why is my connection closed?
> 
> Thanks a lot in advance,
> Antonis

In response to

pgsql-odbc by date

Next:From: Hiroshi InoueDate: 2006-08-30 00:03:12
Subject: Re: [COMMITTERS] psqlodbc - psqlodbc: Fixed dllname of win32
Previous:From: noreplyDate: 2006-08-29 20:25:18
Subject: [ psqlodbc-Bugs-1000720 ] SQLGetInfo SQL_DATABASE_NAME no info

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group