Thread: Transaction Rollback problen (3.0 Protocol)

Transaction Rollback problen (3.0 Protocol)

From
Carlos Guzmán Álvarez
Date:
Hello:

I'm having a little problem with my .net data provider for postgresql 7.4.

I'm executing a little sample that does:

1. Connect to the server.
2. Start transaction.
3. Execution of an invalid SQL command.
4. Catch exception and rollback transaction.

After send the rollbact transaction command i'm not receiving any 
response from the server, instead, if the SQL command is a valid SQL 
command all runs fine, any idea about what can be the problem ??


Thanks in advance.



--
Best regards

Carlos Guzmán Álvarez
Vigo-Spain




Re: Transaction Rollback problen (3.0 Protocol)

From
Tom Lane
Date:
Carlos Guzmán Álvarez <carlosga@telefonica.net> writes:
> After send the rollbact transaction command i'm not receiving any 
> response from the server, instead, if the SQL command is a valid SQL 
> command all runs fine, any idea about what can be the problem ??

Are you using the extended query protocol?  If so you probably have
forgotten the need for a Sync message.  After an error, the server
discards frontend messages until it sees a Sync.  This is needed so that
you can fire off several component messages in an extended-query
operation without waiting to see whether each one succeeds.  You put the
Sync at the point where you want to wait for results.
        regards, tom lane


Re: Transaction Rollback problen (3.0 Protocol)

From
Carlos Guzmán Álvarez
Date:
Hello:

> Are you using the extended query protocol?  If so you probably have
> forgotten the need for a Sync message.  

You are right, thanks very much, it's working well now.





--
Best regards

Carlos Guzmán Álvarez
Vigo-España