|
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
Stay one step ahead of the competition. Evaluate and give feedback
on some of the hottest web development tools on the market today.
Make your opinion heard! Click
Here
|
|
#1
|
|||
|
|||
|
Record locking question...
I've got a small database that has two tables that gets updated pretty often.
One table has a record that is updated very often. The last update is always the correct one, so conflicts are not an issue. But collisions might be. The other table requires a lot of deletions. This is a modification to the "users online" code found at this site at http://codewalkers.com/tutorials/14/1.html. What sort of locking (if any) do I need to even implement for these tables? Thank you! |
|
#2
|
|||
|
|||
|
RE: Record locking question...
I wouldn't worry about any locking. Let the database engine handle that for you...
|
|
#3
|
|||
|
|||
|
RE: Record locking question...
That sounds good, but I have seen a few instances where the error code was visible on my site when the process failed. Is there a way to retry the operation to make sure it completes?
Thanks |
|
#4
|
|||
|
|||
|
RE: Record locking question...
You could use transactions....if you are using MySQL, you would need to use a table type of InnoDB.
|
|
#5
|
|||
|
|||
|
RE: Record locking question...
Thanks.
|
![]() |
| Viewing: Codewalkers Forums > Other Technologies > Database Help > Record locking question... |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|
|
|
|