I'm trying to figure out the best way to validate a unique_together
constraint. The relevant parts of the model are here:
------------------------------------------
class Thesis(models.Model):
thesis_name = CharField('Thesis Name', maxlength=50,
core=True, validator_list=[???????])
thesis_owner = models.ForeignKey(User, editable=False)
def save(self):
if not self.id:
self.thesis_owner = threadlocals.get_current_user() ***
super(Thesis,self).save()
class Meta:
unique_together = (("thesis_name", "thesis_owner"),)
*** - using the threadlocals middleware from Luke Plant
http://lukeplant.me.uk/blog.php?id=1107301634
-----------------------------------------
I'm using the standard django admin interfaces. The thesis_owner
field is populated automatically with the user info, but not until
after user inputs have been validated. So the standard
unique_together validation doesn't catch duplicate entries. They
aren't caught until the database issues an IntegrityError, generating
a fatal error to the user. Instead I'd like to raise the standard red
error banner with a message like "A thesis already exists with name
XXXXX. Please choose a different name".
Possible solutions:
1. Add a custom field validator to validator_list -
Field validator will only check at the individual field level where
information about the model instance (i.e. User info) isn't in
context. Also, there doesn't seem to be a good way to find out
whether it is an "add" or a "change" operation, which need to be
handled differently. Any way to get this out-of-context information?
2. Custom uniqueness check in the model's save method -
This approach allows for access to user info and checking for "add" or
"change" (see above). However, the save happens after the view's
error checking has completed, so raising a ValidationError at this
stage results in a fatal browser error rather than the red error
banner. Is it possible to cause save to raise the red banner instead?
3. Supplement the user info into the POSTed data before it is passed
to the validation -
Theoretically the standard manipulator_validator_unique_together
function will catch the error. Can this be done through a custom
manager or manipulator or in some other way that doesn't require
changes to the admin views, models, etc.?
Thanks! Any insight is appreciated.
Mark
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
