OMG, call it "3:15AM syndrome"
Thank you J.
--~--~-~--~~~---~--~~
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, sen
On 12/12/07, l5x <[EMAIL PROTECTED]> wrote:
>
> Unfortunately, it creates second record, when using your solution,
> instead of updating.
Well then instead of instantiating a new object will 'Full()', why
aren't you getting an existing object and passing it into the form
instead of a new object?
Unfortunately, it creates second record, when using your solution,
instead of updating.
--~--~-~--~~~---~--~~
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@googlegro
On 12/12/07, l5x <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I have a model with two ForeignKeys (User and another model). I cannot
> set them to editable=False, because Admin needs to see them and
> modify.
>
> So I've created ModelForm and excluded those two fields. And now:
>
> 1) when I'm tryin
4 matches
Mail list logo
