Yes .. it is ok - the data that I allow to get updated like this is not that important
and when a update is made it
would be two people entering the same data anyways.
It is just for contact info for people in the db ... like there current phone or
address if it changes.
Michael.
On Fri, 9 J
"John W. Holmes" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Michael Gale wrote:
> > For the UPDATES ... what would have it in theory two people hit the
UPDATE
> > button at the exact same time ? Would one just over write the other ...
> > cause that is fine ?
Hi Michael,
is it
Michael Gale wrote:
For the UPDATES ... what would have it in theory two people hit the UPDATE
button at the exact same time ? Would one just over write the other ...
cause that is fine ?
Whatever UPDATE gets there first will execute and the other one will
wait until it's finished to update. Ther
Hello,
I have a web app that uses a mysql database, now lots of INSETS and
UPDATES are done on a daily bases. Now I do not want to start locking
tables. For the INSERTS it is just a plain insert with a auto incrementing
primary key. So I am sure that multiple inserts would not have a problem is
m
