|
That depends on the requirements of the
system. Largely, plain old DB transactions take care of any concurrency
issues we have. In the rare instance that “dirty” updates are
not allowed, we have a dt_updated field in the table in question, which we read
and save in a hidden field when populating the “edit” form.
During the update process, we pass this value back into our update
procedure. The update procedure then checks that value against the value
stored in the database – if they match, the update is committed. If
they don’t match, we display the new information to the user along with
the information they entered and ask them if they still want to commit the
changes. It works pretty well. In most areas of our application though,
we don’t care about dirty updates, since the fact that the data may have
changed would never cause the user to want to reconsider his update. In the end, it all depends on your
business requirements. Roland From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Scott Ok I am working on an
application that is a multi user intranet application, the current system works
on the basis that last in wins on the storage of the data placed back to the
database. I was wondering what
other people do to prevent this, like record locking. I was reading a few
articles on MSDN about the 3 types of record locking available, but wanted to
know how others approached or dealt with the subject as well. Any help or further
discussion would be great. Regards From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roland Collins What particular aspects? SQL
concurrency is a pretty large topic, depending on what aspects you’re
referring to. You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected] |
- RE: [CFCDev] Repost: SQL Concurrency Roland Collins
- RE: [CFCDev] Repost: SQL Concurrency Barry Beattie
- RE: [CFCDev] Repost: SQL Concurrency Andrew Scott
- RE: [CFCDev] Repost: SQL Concurrency Barry Beattie
- RE: [CFCDev] Repost: SQL Concurrency Nat Papovich
- Re: [CFCDev] Repost: SQL Concurrency Bill Rawlinson
- RE: [CFCDev] Repost: SQL Concurrency Barry Beattie
- RE: [CFCDev] Repost: SQL Concurrency Andrew Scott
- RE: [CFCDev] Repost: SQL Concurrency Barry Beattie
- RE: [CFCDev] Repost: SQL Concurrency Barry Beattie
- Re: [CFCDev] Repost: SQL Concurrency Jared Rypka-Hauer - CMG, LLC
