I'm working on a project which for the purposes of this conversation
we could say is about authors writing and sharing books.
My tendency is to want to make an app called "people" and an app
called "books," as these are two different models in my mind. A
person has certain attributes which would be defined in the "person"
model, and the book has certain attributes which would be defined in
the "book" model.
For some reason it's weirding me out to put these in the same app. I
think because seeing tables like people_book or books_person doesn't
feel right. I imagine something more like:
books_book
books_genre
people_person
people_group
people_person_contacts
But I need to make the link between the author (person) and the book.
In the django docs I see that you can easily make a foreign key by
referencing the model:
manufacturer = models.ForeignKey('production.Manufacturer')
...but it feels like maybe stepping outside the "django way."
I know there's no definitive answer, but at what point do you
typically decide that something belongs in it's own app? Is it
typical to dump everything into a single app?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
