Evert | Rooftop wrote:
Reading all this I suddenly realise I have the same problem. I'm using a
modified tree traversal alghoritm to store my tree in the database, but
when I insert a new node I assign new ID's based on a SELECT query.
I think I can deal with it with the combined UPDATE..SELECT
On Sun, 2005-08-28 at 15:58, Satyam wrote:
> "Robert Cummings" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> > On Sun, 2005-08-28 at 06:10, Jasper Bryant-Greene wrote:
> >> Dave Carrera wrote:
> >> > If multiple users hit the php app at the same time how do i ensure that
> >> > t
Reading all this I suddenly realise I have the same problem. I'm using a
modified tree traversal alghoritm to store my tree in the database, but
when I insert a new node I assign new ID's based on a SELECT query.
I think I can deal with it with the combined UPDATE..SELECT query. Right
now an ano
"Robert Cummings" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> On Sun, 2005-08-28 at 06:10, Jasper Bryant-Greene wrote:
>> Dave Carrera wrote:
>> > If multiple users hit the php app at the same time how do i ensure that
>> > the correct amount of stock is taken from stock so that
On Sun, 2005-08-28 at 06:10, Jasper Bryant-Greene wrote:
> Dave Carrera wrote:
> > If multiple users hit the php app at the same time how do i ensure that
> > the correct amount of stock is taken from stock so that a users does not
> > accidentally sell from stock which has already been sold.
>
Dave Carrera wrote:
If multiple users hit the php app at the same time how do i ensure that
the correct amount of stock is taken from stock so that a users does not
accidentally sell from stock which has already been sold.
Even though multiple users may hit the PHP app "at the same time" (even
6 matches
Mail list logo
