Thanks a lot for the explanations Alan. That really helped.
Bernard On 1/19/06, Alan Franzoni <[EMAIL PROTECTED]> wrote: > Bernard Lebel on comp.lang.python said: > > > I'm absolutely flabbergasted. > > As I told you, i think this is related to the isolation level - I really > think it's a feature of the DB you're using - this way, until you commit, > your database lies in in the very same state on the same connection. > Suppose you make one query, and then you make another one, and you then > decide, on these result, to take a certain action on your DB; in the > meantime (between Q1 and Q2) another user/program/thread/connection might > have done a different operation on the very same db, and so you would be > getting a Q1 results from a certain state in the DB, while Q2 from a > different state, thus misleading you to take an inopportune action. > > committing the connection syncs the state you're looking at with the actual > DB state. > > -- > Alan Franzoni <[EMAIL PROTECTED]> > - > Togli .xyz dalla mia email per contattarmi. > Rremove .xyz from my address in order to contact me. > - > GPG Key Fingerprint: > 5C77 9DC3 BD5B 3A28 E7BC 921A 0255 42AA FE06 8F3E > -- > http://mail.python.org/mailman/listinfo/python-list > -- http://mail.python.org/mailman/listinfo/python-list
