|
|
|
| laziness, impatience, and hubris | |
| PerlMonks |
Re^2: Implementing rowlockingby smithers (Friar) |
| on Jan 09, 2007 at 20:45 UTC ( [id://593792]=note: print w/replies, xml ) | Need Help?? |
|
The optimisitic locking is a solid way to approach this. I would not devise a custom/app-specific locking strategy inside the database as you described earlier. That's just prone to more issues, complexity and maintenance.
Regardless of Rdbms vendor locking or your custom locking, holding a lock for 5+ minutes is too long on a busy system. Seems that would lead to transaction blocking or even deadlocking. Good luck with your project.
In Section
Seekers of Perl Wisdom
|
|
||||||||||||||||||||||