I dropped the table again, and changed the fields in my model from DecimalField to FloatField. Now it works, it'll display the proper option that's been selected. However, when I try to save it on the form I created in my view, it'm getting this error:
http://dpaste.com/153802/ Ugh. Ha On Feb 2, 1:03 pm, Chris McComas <mccomas.ch...@gmail.com> wrote: > Nope. I dropped the table completely and started from scratch. I'm > still testing it out, so there hasn't been any real data entered so I > can play around with it. I dropped the table, uploaded my new models, > syncdb, and then filled out a form, saved it. It saved properly, went > back to edit the form and it's still not showing anything as > <selected> for ha_grade or hp_grade. The <select> drop-down for each > still lists the value as 4.33 or 4.0 or 3.67 etc? > > On Feb 2, 12:51 pm, Shawn Milochik <sh...@milochik.com> wrote: > > > > > On Feb 2, 2010, at 12:48 PM, Chris McComas wrote: > > > > Like this? > > > >http://dpaste.com/153790/ > > > Yeah. Does that help with the pre-population in your form? > > > Shawn -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
