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 you are only left with the ForeignKey" process. > > I'll see if I can do that.
FYI, I can reproduce two problems in a smaller complete project (enclosed), although I haven't had success creating a minimal case. Steps to reproduce the main problem: 0. create a database 1. syncdb 2. run the dev server 3. go to http://localhost:8000/admin/ and login 4. create a new Session object 5. fill in all required fields, creating a Speaker and TimeDivision as needed. leave Track as '------' 6. Save How to make it work: 7. Set primary_key=True on the 'name' field of the Track object 8. AND add blank=True to the 'track' field of the Session object 9. delete the database 10. repeat Note that without blank=True, the Session with no track won't validate. 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 and (I think) also without null=True) so I can still use the data. Thanks, --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
djtest.tar.bz2
Description: Binary data
-- Dave Abrahams Boost Consulting www.boost-consulting.com
