On 10-09-11 12:52 PM, Tamara Temple wrote:
I have a general question and am looking for best practices.
Suppose I present a user with a form for editing an entry in a table,
i.e., the form has filled in values from the existing table entry.
Now, suppose they click on 'submit' without making any changes in the
form. (Perhaps, say, rather than clicking 'Cancel' or 'Return to Main'
or some other option which would get them out of that screen without
submitting the form).
Is it worth the overhead of passing along the previous values in the
table in hidden fields so that fields can be checked to see if they've
been updated or not after the submit? Or is it worth reloading the old
values from the table to check against the newly submitted form? Or is
all that overhead not worth the time because an update that overwrites
existing values with the same values is not that onerous?
(Is that question clear enough?)
I use database table to object mapping classes. The base class sets a
dirty bit if a field actually changes. If an attempt is made to save the
data and no dirty bits are set, then the save method returns true for a
successful save, but no commit to database is made since nothing has
changed. In this way I never think about the problem beyond the original
implementation of the base class.
E-Mail Disclaimer: Information contained in this message and any
attached documents is considered confidential and legally protected.
This message is intended solely for the addressee(s). Disclosure,
copying, and distribution are prohibited unless authorized.
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php