[Fwd: Re: [PHP] DB access and sessions]

2005-08-18 Thread Sabine
Uups, forgot to send my answer to Bret to the list too. Sabine --- Begin Message --- Hello Bret, I think Terences solution is good, if you have a lot of concurrency on your documents. But if the concurrency is less and it is unlikely that 2 people edit the same document at the same time, I'll

Re: [PHP] DB access and sessions

2005-08-17 Thread Terence
We use a combination of timeout and user who has locked the record in a form e.g. User A opens the form. A record id is stored in the page and the db record has 3 cols -> is_locked (y/n), locked_by (user_id) & locked_time (datetime) B then opens the form. If the record is locked & more then

Re: [PHP] DB access and sessions

2005-08-17 Thread Tyler Kiley
Since you can't be sure to be notified when a user stops editing a page, whatever solution you choose will probably involve some sort of timeout-based system. (e.g. when someone starts editing a page, set a "last_opened" time field on the resources, and when someone else tries to edit the same pag

[PHP] DB access and sessions

2005-08-17 Thread Bret Walker
Hello- I'm developing a web-based system whereby users can edit documents and then e-mail the documents to selected recipients. The "documents" are comprised of the data from several MySQL fields. I want to make sure that two people don't edit a document at the same time. My users log in via a