Again, this is my view: http://dpaste.com/153735/
I'm thinking the error is in someway related to this line: new_green.hp_coursepoints = new_green.hp_grade * hp_credithours The only thing I changed was changed hp_grade from a DecimalField to FloatField On Feb 2, 1:14 pm, Chris McComas <[email protected]> wrote: > 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 <[email protected]> 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 <[email protected]> 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 [email protected]. 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.
