I successfully used inspectdb to create my initial models from a MySQL DB, I had to tweak it a bit but in general I was quite happy. Tweaking was esp. necessary for the auto-increment fields, which were generated as IntegerField() but should have been AutoField(). But that was just a side note.
DB views I have views in my DB (MySQL5). Implementing models for them is not problem, but until now I was able to run "syncdb" but once I have created the views as models "syncdb" will probably try to generate the ManyToMany-table that those views use. How can I tell it to leave the view alone. Actually I also had the hope to give all the DB schema management away to Django, but this makes me realize I can't. Or am I wrong? (I am not too deep into Django yet). Constraints My schema uses constraints and cascading deletes, etc. Is that a good idea to use with Django? Is there a way to tell Django to maintain those using the given relationships defined in the models? Schema management I had modified my schema a bit and ran "syncdb" again, but no change happened. I had simply added a new column to a couple of tables. Is it true that Django doesn't do that for me? Otherwise it's nice how quickly you can get productive with Django, nice job. I am just waiting for the integration of SQLAlchemy -- Wolfram --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
