> I guess by "bug" I meant that > > synchronizing, by its nature involves making two disparate things > congruent. > > syncdb does not do that.
Well, it does, up to the part that 'it' (the writers) feels confident about: it synchronizes the database globally with newly added models; indeed not per table. The bug would be mostly in the name then, but I guess 'create_new_tables_for_new_models_only' was a bit too unwieldy. And perhaps a future release would be able to have this (probably much wanted) additional feature. Other people should be able to elaborate on that. > but ok, thanks for the reply, I'm glad its a documented "feature" at > least... > > On Thu, Mar 27, 2008 at 10:37 AM, bavel <[EMAIL PROTECTED]> wrote: > > That's what I had done: deleted the database and run syncdb again - so > I was pretty sure that the database file reflected the class in my > models.py. I entered one record manually through the admin interface > and got the error when I clicked 'Change' for this table. The first > field in the table should have name 'nummer' and I imagine it got > abbreviated somehow - but I do not know enough about sqlite to be able > to check this. (Sqlite's online help is a bit vague about inspection > of the table structure). > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
