Hi, On 8/11/07, Russell Blau <[EMAIL PROTECTED]> wrote: > Basically, I want to keep track of every email address that has ever > been registered with my app, to prevent duplication. By overriding > delete(), I prevent any address from being removed from the database, > but I also have to prevent editing the address once it has been > registered. The problem is that "editable=False" works too well -- it > prevents an admin from editing an existing address, but also prevents > them from adding new ones. Is there a way to set up my model so that > the administrator can enter new email addresses for a user, but cannot > change the existing ones?
__setattr__ or property which sets the email only if it is None? I'm not sure, but this could work. :) > Russ Kai --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
