Glenn Tenney <gt-django <at> think.org> writes: >
> 2. In Rails you need to declare your SQL code *and* tell Rails about > your schema, but in Django it's all very nicely put into an object > oriented description in your model. A big win, to me, for Django. Rails has something called migrations (see http://wiki.rubyonrails.com/rails/pages/UnderstandingMigrations). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
