Re: Django apps and models

[andy]

Thanks for the advise, I had considers this option, and I really dose
seem that apps are move for generic features as you pointed out but I
have about 10 tables which are as depended in structure as the ones
noted above. I really don't what to have too much code in one view.py
or model.py file. For now I plan to create a customer app without the
ForeignKey relationship, work on it and when I add the branch model I
add the relationship that links them. Probably a bad idea but thats
the bes I have so far, this is something I'll need to think about a
bit more though.

Thanks for your 2c

Kimani

On Nov 5, 8:37 am, derek  wrote:
> I'll add my 2c here...
>
> I don't think you need to create an app for this (not yet).  Just
> create a normal Django project and go from there.  Apps are more meant
> for very generic types of functionality that can be used in many, many
> situations e.g. tagging.
>
> Your design is still very broad and so hard to comment on.  You may
> want to consider a many-to-many between customer and branch.  Then you
> can add data for each without being dependant on either existing
> first.  This also gives you the flexibility to link up the same
> customer to many branches.
>
> On Nov 4, 6:24 pm, andy  wrote:
>
> > 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 django-us...@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django apps and models

[derek]

I'll add my 2c here...

I don't think you need to create an app for this (not yet).  Just
create a normal Django project and go from there.  Apps are more meant
for very generic types of functionality that can be used in many, many
situations e.g. tagging.

Your design is still very broad and so hard to comment on.  You may
want to consider a many-to-many between customer and branch.  Then you
can add data for each without being dependant on either existing
first.  This also gives you the flexibility to link up the same
customer to many branches.


On Nov 4, 6:24 pm, andy  wrote:
> 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 django-us...@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Django apps and models

[andy]

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 django-us...@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.