Ian Holsman wrote:
> all of these types of things should get as much info as possible out > of the database/models that exist > having to retype the relationships sounds yuko to me. > > but hey... I'm not a ruby guy.. maybe they like doing these kind of > things. This is a limitation of supporting multiple databases (not to start a flame war, but many more databases than Django). Really, though, if you have a legacy schema of several hundred tables, it does get to be a pain. Less aggravating, though, than rekeying EVERY field in Django if introspection fails. So, I guess it depends on your philosopy: should schemas be written in code (Django), or written by your database architect in SQL(Rails). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
