Karen,

Thank you.

Based on your answer, I continued looking for problems in my code and
in my setup.

Firstly, the strings in the values of the choices were of length 7 and
the CharField was of length 6. I was helped by a coworker to fix that.
Then the problem of not showing the save'd choice persisted, and my
coworker realized that the field was created in the database with
another user as the one with which the program was talking to the
database. Fixed that, and the problem went away.

best,

Haroldo

On 16 oct, 10:05, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
> On Thu, Oct 16, 2008 at 1:43 AM, [EMAIL PROTECTED] <
>
> [EMAIL PROTECTED]> wrote:
>
> > hi,
>
> > When I instance a ModelForm with a record of its base model, there is
> > a CharField with "choices" that doesn't show the stored value in the
> > combobox. Is this expected behaviour?
>
> No.  Details of your model, form definition, what's actually in the DB and
> what gets displayed in the combo box might help someone pinpoint what's
> going wrong in this case.  As it is all I can tell you is the combo box
> should have the value from the DB show as the choice selected when the form
> is displayed.
>
> Karen
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to