> I don't see your point here. > - race condition is a concurrency problem involving the database, > - Concurrency management is handled by the database engine, > - SQL is simply a language that can be used to interact with > the database, > - then, why SQL shouldn't provide tools to help the > programmer tell the database > engine where Concurrency may happen and should be avoided?
Every SQL statement can potentially run in a concurrent environment! If we had to deal with the mechanics of that directly within every SQL statement we write, SQL would be much more difficult to write. Instead, we tell the database what outcome we want, and we let the database figure out the implementation details. Likewise, SQL would be more difficult if we had to talk about leaves, pages, extents, etc. instead of tables and fields. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:252571 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
