base between SELECTs. The only time
> the user would be aware that what (s)he thinks of a transaction is not the
same as the RDBMS' view!
>
> =dn
>
>
>
> > Or not?
> >
> > Ollie
> >
> > -----Original Message-----
> > From: DL Neil [mailt
ent: 02 February 2002 15:40
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Php-Db ML
> Subject: Re: [PHP-DB] Ensuring users don't overwrite each other (NOT a
> newbie question)
>
>
> Ollie,
>
> Probably easier to repeat the 'read' (from the first population of the u
.
Or not?
Ollie
-Original Message-
From: DL Neil [mailto:[EMAIL PROTECTED]]
Sent: 02 February 2002 15:40
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Php-Db ML
Subject: Re: [PHP-DB] Ensuring users don't overwrite each other (NOT a
newbie question)
Ollie,
Probably easier to repeat
ruary 2002 15:40
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Php-Db ML
Subject: Re: [PHP-DB] Ensuring users don't overwrite each other (NOT a
newbie question)
Ollie,
Probably easier to repeat the 'read' (from the first population of the user
form) - and then do the
comparison(s) in
ML" <[EMAIL PROTECTED]>
Sent: 01 February 2002 15:23
Subject: Re: [PHP-DB] Ensuring users don't overwrite each other (NOT a newbie question)
> Yes thats an interesting idea, and this compare-and-modify-if-unchanged bit
> would be implemented via SQL IF statement(s) perhaps?
&g
Yes thats an interesting idea, and this compare-and-modify-if-unchanged bit
would be implemented via SQL IF statement(s) perhaps?
Thanks
Ollie
"Hugh Bothwell" <[EMAIL PROTECTED]> wrote in message
news:<[EMAIL PROTECTED]>...
>
> "Oliver Cronk" <[EMAIL PROTECTED]> wrote in message
> [EMAIL PROTE
"Oliver Cronk" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Thanks for that answer, you filled in some of the blanks for the table /
> logging solution, but I am now looking at row locking instead of a
seperate
> table (and then doing things similar to what
y 2002 08:30
> To: Peter Lovatt; [EMAIL PROTECTED]
> Subject: RE: [PHP-DB] Ensuring users don't overwrite each other (NOT a
> newbie question)
>
>
> Thanks for that answer, you filled in some of the blanks for the table /
> logging solution, but I am now looking at row locki
]
Sent: 01 February 2002 08:10
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: [PHP-DB] Ensuring users don't overwrite each other (NOT a
newbie question)
Hi
Interesting problem! Systems would be so much easier to build if we didn't
have to allow for users :)
Two suggestions, depending
Hi
Interesting problem! Systems would be so much easier to build if we didn't
have to allow for users :)
Two suggestions, depending on how you want the data dealt with.
A table of rows in use, with a time stamp and an owner. When user1 opens the
record, stamp it with owner and time. If user2 w
10 matches
Mail list logo
