Okay, I asked the web host guys and this is what they said:
"Hi Jenifer, we only use single instances of MySQL so the master/slave
replication issue would not be possible. As far as I know, the only way a
delayed update could occur would be if you had multiple updates queued
behind a
Hello.
>So now my question... is it possible that MySQL didn't execute that first
>UPDATE query on
>that first page until after the rest of the process completed?
>...
>- Every page has UPDATEs, INSERTs, or DELETE commands so I'm wondering
>whether the
hmmm... let me ask the guys how they have it all set up.
Jenifer
- Original Message -
How is your MySQL installation set up? At my company, we have a
master server and several slaves replicating off that master. All
inserts/updates go to the master, and all selects go to the slave
> So now my question... is it possible that MySQL didn't execute that first
> UPDATE query on that first page until after the rest of the process completed?
>
> - The customer page is a basic form that posts the information to itself
> with a simple UPDATE command and then goes to the next page
Hi all,
I'll give you a little background so that my question is put into context.
I've already posted this question to my local programmers message group and
they said to post it here. So, here it goes:
I have a phone order system that I wrote in PHP. It has a series of pages
starting with
Hi,
does anybody know how to make a delayed update and is this implemented in
mysql 3.23.x ? the update should not block the client (i guess this does
low_priority) if the table is a lot in use. simply update the rows later,
just like insert delayed does.
Thanks,
Corin
