it really is that - simultaneous transactions are isolated from one another,
and their results are only made visible to other transactions after they're
committed. as far as locking, you generally choose between an "optimistic"
and a "pessimistic" approach:
Thanks.
Ok, so I found an article that talks about the different locking types for
databases:
* lock everything
* don't lock but check if the data changed on you and fix it if it did
* don't care -- only use for single db connection
Now, where does SQLAlchemy fit into all of this? Also, I notice PostgreSQL had
2 different locking strategies you can use and the info I am looking at now
suggests I am going to have do some complex database handling to check for data
integrity. Of course, the whole point of SQLAlchemy is to abstract away from
such low level database interaction... is it not?
Since I'm guessing everyone who uses a db must deal with this problem that much
mean there is some information I am missing or something I don't understand
that everyone else out there just knows about. :)
_________________________________________________________________
Hotmail: Trusted email with powerful SPAM protection.
http://clk.atdmt.com/GBL/go/177141665/direct/01/
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en.
