Hello all,
I'm wondering if the following behavior is a feature, a bug, or a
coding error on my part: when I define a model with a CharField that
has choices, if I later save an instance of the model with a value for
that field which is not one of the choices, the value does not display
in the admin, not even in "static" representations, such as the list
display. For example:
class Transaction(models.Model):
MEMO_CHOICES = (('payment', 'Payment from client'), ('adjustment',
'Other adjustment'),)
memo = models.CharField(max_length=80, choices=MEMO_CHOICES,
blank=True)
# etc...
class TransactionAdmin(admin.ModelAdmin):
list_display = ['memo', 'amount']
>>> Transaction.objects.create(id=1, memo="Some other value")
Then, if I visit the change list page for Transactions in the admin,
the Memo column of the table displays "(None)" for the Transaction
with id 1, even though the correct value ("Some other value") is
stored in the database.
I can see why you wouldn't display the other value in the <select>
widget for the memo field in the change page for that item, but it
would be nice in my case to see the actual value, regardless of
whether it is a valid choice or not, on pages where the user can't
actually change it. If this is the expected behavior, however,
suggestions for a workaround would be welcome!
Any insight would be greatly appreciated.
Thanks,
Richard
--~--~---------~--~----~------------~-------~--~----~
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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
