I posted a ticket (#1972) a while ago and there's been a few other
tickets reporting the same issue, so it sound like an issue that
should be addressed.
Basically: A model with no explicit fields doesn't get created by
syncdb, but syncdb doesn't throw any warnings or errors. Consider the
following:
---
class SignupList(models.Model):
# Has many SignupSlot objects
pass
class Event(models.Model):
list = models.OneToOneField(SignupList)
class SignupSlot(models.Model):
parent = models.ForeignKey(SignupList)
---
(i.e. Every event has a signup list, which has a one-to-many
relationship with signup slots.)
I have two ideas on how this could be addressed:
1. Throw a warning or error in Syncdb, letting the user know that
every model must have at least one explicit field.
2. Build the field as the programmer defined them.
Any ideas?
-Tyson Tate
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@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-developers
-~----------~----~----~----~------~----~------~--~---
