Re: [PHP-DB] Ensuring users don't overwrite each other (NOT a newbiequestion)

This is good brain-storming guys! Better to use an integer rather than a date field as 2 simultaneous transactions can still occur on the same second; most date time fields are accurate only to the nearest second. Good point, John. However MySQL (AFAIK) does not have any time functions

Re: [PHP-DB] Ensuring users don't overwrite each other (NOT a newbiequestion)

Hi, This is a technique I first saw in the O'Reilly book Oracle Design. The idea is to use integers rather than dates, and treat the integers as semaphores (or latches in Oracle terminology). This technique is very portable as it does not require date types. Create an integer column called

RE: [PHP-DB] Ensuring users don't overwrite each other (NOT a newbiequestion)

Lim [mailto:[EMAIL PROTECTED]] Sent: 02 February 2002 20:09 To: [EMAIL PROTECTED] Subject: Re: [PHP-DB] Ensuring users don't overwrite each other (NOT a newbiequestion) Hi, This is a technique I first saw in the O'Reilly book Oracle Design. The idea is to use integers rather than dates, and treat

Re: [PHP-DB] Ensuring users don't overwrite each other (NOT a newbiequestion)

Are you guys interested in yet another solution? It simular but I think it's even easier if that's an incentive... -In your table do put a datetime field, I'll call it lastMod. This will be the last updated date and time (you need time here) -In your form have this as a hidden field so it

Re: [PHP-DB] Ensuring users don't overwrite each other (NOT a newbiequestion)

Hi Better to use an integer rather than a date field as 2 simultaneous transactions can still occur on the same second; most date time fields are accurate only to the nearest second. Regards, John Frank Flynn [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... Are