Hi guys, Say I have a CUSTOMER, BRANCH and a SALES table for my project design.
Question, should is it wise to create a customer, branch and sales app. I like this idea of doing this but I have a few issues. 1. If I create a customer app and create a Customer model class that has a ForeignKey relationship with the branch table, I would seem that I have to create the branch application first and create its Branch model class. 2. Also what if I plan for some reason to populate the branch table using the admin interface, to avoid creating a view and templates for it. Would I still make sense to create app just to host possibly one model. What came to mind what to create a app that only manages all the database table or at least just table like branch which I don't plant to create views for. I guess this is what generally happens in the MVC frame works that are now app oriented like django. I like the django Idea of having models in the apps at it seems more portable, so I would like to keep things this way as much as possible which is why I as seeking some advise on how to possibly deal with this kind of situation. Maybe my opinion of an app is flawed is some way, which is why I am having this issue. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. 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.
