* Thus wrote anders thoresson ([EMAIL PROTECTED]):
set_lock($table_name, $row_id), check_lock($table_name, $row_id) and
release_lock($table_name, $row_id). Whenever an editor opens some content
for editing, check_lock() will be called to se if table_lock contains a row
with the same
What happens when the user doesn't finish editing or the browser
simply crashes on him?
Well. Didn't think of that.
So how can I avoid that two editors loads the same record for editing at
the same time, while still making all records available for regular
visitors to read?
--
anders thoresson
Hi,
For an application that I'm working on, I wan't users to be able to show
content even while an editor/administrator makes changes in one of my
database's tables. But if another editor tries to load the same content for
editing, he/she shouldn't be able to do this.
I've been reading up on
3 matches
Mail list logo