[thelist] MYSQL SELECT, UPDATE and INSERT priority

Joshua Olson joshua at waetech.com
Tue Feb 24 09:39:00 CST 2004

> -----Original Message-----
> From: eduardobk at via-rs.net
> Sent: Tuesday, February 24, 2004 6:34 AM
> Hi all.Here's the problem I've got with MySQL:1. Click on a
> record (through the PHP software I'm developing) to edit it2.
> Change some fields3. Submit4. When back to the same record (just
> submit it to save changes) all fields are with old values.5.
> Press F5 and everything is OK with changed saves.I've found out
> that UPDATE is occuring after the new SELECT (or SELECT is
> occuring before UPDATE) so that the old values are still
> returned.My first idea is to use the values from the from and not
> from the SELECT (database) after submit. So I'd get the real
> values.But I'd like to find out some database side solution since
> this is not good at all :(


I normally try to just answer the questions... but, in this case, I must

Why do you not want to update then select?  Or, better yet, update and then
redirect to the form again (which will select and display) so that F5
doesn't repost?

Joshua Olson
Web Application Engineer
WAE Tech Inc.

More information about the thelist mailing list