I'm on an interesting thread right on in a discussion group in SQL Server
worldwide user's group.
They insist that you need to maintain rowlocks when you read database
records for applications such as ticketmaster where you would lock a record
so no one else can take it. I understand the need for transaction locking
and the like for inserts and updates, but I don't understand why they insist
that you need to maintain record level locking. And I haven't the faintest
idea how you would release these row locks in a stateless environment like
the web.
Has anyone here used rowlocks on selects successfully? It seems like what
they are saying is impossible.
Costas Piliotis
Programmer
Voyus Canada Inc.
T: (604)419-5655
F: (604)419-4494
Email: [EMAIL PROTECTED]
************************************
Quiet, Pinky; I'm pondering.
_ _
/~\\ \ //~\
| \\ \ // |
[ || || ]
] Y || || Y [
| \_|l,------.l|_/ |
| >' `< |
\ (/~`--____--'~\) /
`-_>-__________-<_-'
/(_#(__)#_)\
\___/__\___/
/__`--'__\
/\(__,>-~~ __)
/\//\\( `--~~ )
'\/ <^\ /^>
_\ >-__-< /_
(___\ /___)
______________________________________________________________________
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
