On 2008-06-12 15:13:23 -0600, Justin Kennedy <[EMAIL PROTECTED]> said: > With Django, as I understand it, the class models have to be developer > first, and it takes care of setting up the db tables. I really prefer > this method, however, I would still like to create my Class Diagrams or > DB Model first so I can visualize the relations between the models as a > whole. It would be nice if I could generate the basic Django models from > a DB Schema/model or Class Diagram or similar tools.
It is common to just start designing your models using Python. Models in Django are written declaratively which enable a very nice syntax for creating database tables and keep it mapped properly in the ORM. > > I tried using manage.py inspectdb but it didn't auto detect the > relations. The basic db is like: > > table: milestone > columns: id, title, due_date > > table: task > columns: id, milestone_id, title, due_date inspectdb is meant to help you get to the finish line and not cross it for you. It does as much as it can, but as you have discovered it has some problems with certain database backends due to their nature. There is no reason to still not use insepctdb. Just convert the foreign keys it missed. For example if it resulted in:: milestone_id = models.PositiveIntegerField() Simply change it to:: milestone = models.ForeignKey(Milestone) The underlying datatype won't need to be changed. This will make sure that the ORM generates the SQL you would expect from a foreign key. -- Brian Rosner http://oebfare.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
