On 5/16/06, Filipe <[EMAIL PROTECTED]> wrote: > Do you think I'll find difficulties in using model classes with my own > data persistency logic? In such case, will I loose other features > besides the ORMapping itself? (I've read something about loosing > autogenerated admin pages, form validations, etc)
Models classes basically == ORM. You can't separate the two. You will lose the Admin system, generic views, and the permissions system, but templates, views, url mapping, caching, etc. will still work. IMO Django's still a great framework even if you don't use it's ORM. You may want to take a look at SQLAlchemy. I've heard it can handle legacy database schemas a lot easier. You can use it with Django, but you still won't get the Admin system, generic views, or permissions. Joseph --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
