Re: Need to examine and act on old vs. new at .save() time

On Wed, 11 Jan 2012 17:26:44 +0000, Tom Evans <tevans.uk@googlemail.com>
wrote:

>On Wed, Jan 11, 2012 at 5:22 PM, Jeff <jblaine@mitre.org> wrote:
>> When Device.netgroups (a M2M field) changes, we need to perform
>> some python-ldap operations.
>
>Have you considered simply going back to the database to check what
>the values currently are? It would be inefficient, but clean and
>concise.
>

I've forgotten how many means of changing this data there are,
but...

If a web-form, would it not be possible to supply the data -- as
normal, in fields to be edited -- AND duplicate the initial values in a
set of hidden fields on the form, so the original and edited fields are
both returned by the form? Then all that would be needed is to compare
the two sets of fields.
--
Wulfraed Dennis Lee Bieber AF6VN
wlfraed@ix.netcom.com HTTP://wlfraed.home.netcom.com/

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.