I fear to get into trouble if I choose to use inspectdb, there are a lot of composited primary keys and many-to many-relations in this DB (I know that the ORM in Django supports m-to-m relations, but knowing it is usually a sensible point in ORMs, I would prefer not to use an ORM just yet).
Still, model classes seem the right place for business logic and data persistency (using my own implementation, bypassing Django's ORM), but I'm reading some contradictory stuff about being able to use model classes without using Django's ORM. I guess the alternative would be to put all the business logic in the views, but that sure doesn't feel right. 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) regards Filipe --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
