-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Well, don't you love when in fact it is YOUR code that's at fault?
Let me assure you that I really tried to blame myself first (did it
for arround 12hours to no avail), but when all else fails...;o)
What I was REALLY doing:
Session1>SET TRANSACTION ISOLATION LEVEL READ COMMITTED; BEGIN;
Session1>INSERT INTO test VALUES(1, 'test');
Session1>COMMIT;
Session1>ROLLBACK;
Session2>SELECT * FROM test;
It seems odd to me that the ROLLBACK was affecting the execution
(couldn't replicate the behavior in psql, maybe its a speed
thing...).
Anyway, many thanks for your time,
Pablo
PS: For anyone who cares, the ROLLBACK was generated by disposing the
NpgsqlTransaction, no matter it was committed. I will post it as a
bug, as Disposing should not be generating that nasty ROLLBACK...;o)
- --
Artificial intelligence is no match for natural stupidity.
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3
iQA/AwUBQGY1Cr6KEogX0AkqEQJi6QCfd9pKE4ShhHyE8bWPcpR0qSuNf1EAoP0h
EF3Ya0/yGI5Bpj9T110coMu+
=+AVZ
-----END PGP SIGNATURE-----
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly
