Erik Vorhes wrote: > There's nothing wrong with parceling out models across different apps. > And unless you're planning on distributing each app separately, don't > worry about cross-app dependencies. > > In this case, I'd encourage you to--since you'll probably want to do > more than just book-related stuff with your people. (The same could be > said about the books.) > > Another reason to have 2 apps for these models is overall growth of > models.py. The more code that's there, the harder it becomes to edit. > (I'm in the process of parceling out a bunch of models myself. Don't > give yourself that headache!)
If you are distributing apps separately you can use conttenttypes and generic relations. http://www.djangoproject.com/documentation/models/generic_relations/ django-tagging django-voting are some apps that use that. Find them on google code. -- Norman J. Harman Jr. Technology Solutions Group, Austin American-Statesman ___________________________________________________________________________ Get out and about this spring with the Statesman! In print and online, the Statesman has the area's Best Bets and recreation events. Pick up your copy today or go to statesman.com 24/7. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
