Hi John,
On Mon, 2007-05-21 at 18:41 -0700, John M wrote:
> i am getting a key error with the following:
>
> sqlite3
>
> class Holding(models.Model):
> portfolio = models.ForeignKey(Portfolio, editable=False)
> symbol = models.CharField(maxlength=10)
> reason = models.CharField(maxlength=200, blank=True,
> null=True)
> shares = models.FloatField(max_digits=7, decimal_places=3,
> blank=True)
>
> class HoldingForm(forms.Form):
> symbol = forms.CharField(max_length=10)
> reason = forms.CharField(max_length=200)
> aimtype = forms.ChoiceField(choices=AIMTYPE_CHOICES)
>
> def update1(request, portid, holdid=None):
>
> objportfolio = Portfolio.objects.get(pk=portid)
>
> if holdid is None:
> modelform = form_for_model(Holding, form=HoldingForm)
I'm not 100% certain what you're trying to do with this line. Normally,
you would only pass in the "form" attribute if you are overriding
methods on the BaseForm class (or providing extra methods). You seem to
be trying to provide some fields as well. What are you expecting to
happen? (You could well be doing something brilliant; I just haven't
seen this approach and I can't work out what it should do.)
> form = modelform()
> else:
> instance = Holding.objects.get(id__exact=holdid)
> modelform = form_for_instance(instance, form=HoldingForm)
> form = modelform(instance.__dict__)
>
> if request.POST:
> form = modelform(request.POST)
> if form.is_valid():
> obj = form.save(commit=False)
> obj.portfolio = objportfolio
> obj.save()
> return HttpResponseRedirect('/holding')
>
>
> when i try to add a new holding, i get a keyerror:
> Request Method: POST
> Request URL: http://127.0.0.1:8000/holding/update1/2/
> Exception Type: KeyError
> Exception Value: 'shares'
> Exception Location: c:\python24\lib\site-packages\django\newforms
> \models.py in save_instance, line 41
>
> any ideas?
The code in newforms/models.py has shuffled around a bit lately, so what
is line 41 in your case? What revision of the code are you using, while
we're at it?
Looking at what might be causing this leaves me confused because we seem
to be checking that all the necessary pieces are in place before we try
to access anything. So if you could fill in the above details (and give
the full traceback -- see below), it might shine some more light on the
problem.
It's probably more useful, too, to post the full traceback, in cases
like this. I can guess that the problem results from the
form.save(commit=False) line in your code, but it would be nice to
confirm that.
A little bit further down the error screen is a link (although it may
not look like a link) marked something like "show cut-and-paste
version". Click on that and you'll get something you can paste into an
email, showing the full traceback.
Regards,
Malcolm
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
