Hello:
Did you figure this out? I can't see any way that a Sync message would
close a transaction started with BEGIN (or START TRANSACTION). It runs
the same code we run at the end of a simple-Query message, and we'd
definitely have noticed if that were causing premature commit ...
Thanks for an
Carlos Guzman Alvarez <[EMAIL PROTECTED]> writes:
> In the extended query mode documentation i see this:
> "Note: Sync does not cause a transaction block opened with BEGIN to be
> closed. It is possible to detect this situation since the ReadyForQuery
> message includes transaction status infor
Hello:
Sorry for late response...
I could finally get Npgsql to talk protocol 3.0 version :) It is not
100% but it is near...
Great !! I'm going to open my code at sourceforge :)
I give it a try in a test similar to yours... I didn't send the create
database commands just the row insertion.
in
Carlos Guzman Alvarez wrote:
Hello:
Hello Carlos.
I continue to work in the implementation of the 3.0 protocol in C#, i'm
making a test that consist on:
- Create a database.
- Create a table in the new database.
- Start transaction.
- Insert 100 rows of data in the new table.
- Commit transacti
Hello:
I continue to work in the implementation of the 3.0 protocol in C#, i'm
making a test that consist on:
- Create a database.
- Create a table in the new database.
- Start transaction.
- Insert 100 rows of data in the new table.
- Commit transaction.
For start a transaction i send a Query m
