The argument against automatic locking sounds like an excuse to me. I've
never understood why they didn't perform automatic locking. Although I
understand the example, I feel it should be up to the user to override the
automatic locking for transactional processing/integrity as this is the
exception and not the rule. After all, isn't this the way SQL functions?
Benjamin S. Rogers
Web Developer, c4.net
voice: (508) 240-0051
fax: (508) 240-0057
>In case someone here isn't subscribed to FusionAuthority News
>Alert:
>
>"Jim Schley, Premier Support, Allaire Corp., has come forth
>with this very important explanation of some of the best
>practices involved with locking shared variables. If you
>don't follow these practices, folks, you may run into some
>unforeseen pitfalls."
>
>http://www.allaire.com/handlers/index.cfm?ID=17318&Method=Full
>
>---------------------------------------------------------------------------
---
>To Unsubscribe visit
>http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
>send a message to [EMAIL PROTECTED] with 'unsubscribe' in
>the body.
----------------------------------------------------------------------------
--
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
