Re: ForeignKey, null, and schema evolution

2007-02-11 Thread David Abrahams
"Ramiro Morales" <[EMAIL PROTECTED]> writes: > On 2/10/07, David Abrahams <[EMAIL PROTECTED]> wrote: >> >> Whatever django bugs may be lurking asid, I need to move forward with >> my project ASAP so I'd really appreciate it if someone could give me a >> few hints about how to evolve my existing

Re: ForeignKey, null, and schema evolution

2007-02-10 Thread Ramiro Morales
On 2/10/07, David Abrahams <[EMAIL PROTECTED]> wrote: > > Whatever django bugs may be lurking asid, I need to move forward with > my project ASAP so I'd really appreciate it if someone could give me a > few hints about how to evolve my existing DB (which was created > without the primary_key=True

Re: ForeignKey, null, and schema evolution

2007-02-10 Thread David Abrahams
"yary" <[EMAIL PROTECTED]> writes: > IIRC, Django's admin can't handle a field with null=True and > blank=False (which is a bit of a shame...) Try adding blank=True to > your model's field? Read my latest post and you'll see that I have tried that. It works, but only if I explicitly specify

Re: ForeignKey, null, and schema evolution

2007-02-10 Thread yary
IIRC, Django's admin can't handle a field with null=True and blank=False (which is a bit of a shame...) Try adding blank=True to your model's field? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users"

Re: ForeignKey, null, and schema evolution

2007-02-10 Thread David Abrahams
David Abrahams <[EMAIL PROTECTED]> writes: > My models.py is enclosed. It doesn't have any special dependencies. > Would you mind trying to reproduce the problem? > >> Try creating a smaller project with a trimmed >> down model -- doing the standard "remove stuff until it starts working >> or

Re: ForeignKey, null, and schema evolution

2007-02-10 Thread David Abrahams
Malcolm Tredinnick <[EMAIL PROTECTED]> writes: > On Sat, 2007-02-10 at 03:34 -0500, David Abrahams wrote: >> >> In my attempt to use >> >>ForeignKey(Track, null=True) >> >> When I actually tried to use a null Track value, I got: > [...traceback snipped...] >> >> ProgrammingError at

Re: ForeignKey, null, and schema evolution

2007-02-10 Thread Malcolm Tredinnick
On Sat, 2007-02-10 at 03:34 -0500, David Abrahams wrote: > > In my attempt to use > >ForeignKey(Track, null=True) > > When I actually tried to use a null Track value, I got: [...traceback snipped...] > > ProgrammingError at /admin/program/session/15/ > ERROR: invalid input

ForeignKey, null, and schema evolution

2007-02-10 Thread David Abrahams
In my attempt to use ForeignKey(Track, null=True) When I actually tried to use a null Track value, I got: Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/django/core/handlers/base.py" in get_response 77. response = callback(request, *callback_args,