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

2002-02-01 Thread Oliver Cronk
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

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

2002-02-01 Thread DL Neil
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

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

2002-02-01 Thread Oliver Cronk
. 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

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

2002-02-01 Thread Oliver Cronk
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

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

2002-02-01 Thread DL Neil
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

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

2002-02-01 Thread Oliver Cronk
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

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

2002-02-01 Thread Hugh Bothwell
"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

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

2002-02-01 Thread Peter Lovatt
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

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

2002-02-01 Thread Oliver Cronk
] 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

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

2002-02-01 Thread Peter Lovatt
[EMAIL PROTECTED] > Subject: [PHP-DB] Ensuring users don't overwrite each other (NOT a > newbie question) > > > > Hi there, currently writing an e-CRM system for an intranet using PHP on > Win32 and MS-SQL. This system needs to be scalable but more importantly > there will

[PHP-DB] Ensuring users don't overwrite each other (NOT a newbie question)

2002-01-31 Thread Oliver Cronk
Hi there, currently writing an e-CRM system for an intranet using PHP on Win32 and MS-SQL. This system needs to be scalable but more importantly there will be anything up to 400 users (unlikely, but the max amount) using the same records (updating information about customers etc) and I worry tha