Hi,
I'm developing an application with several services/modules, every module
is structured into several apps. I'm planning to use the following
directory structure:
project/
module1/
app1 (!)
app2
app3
module2/
app1 (!)
app4
app5
Both modules contain an application called app1, and I would like
module1.app1 and module2.app1 to both contain models of the same name.
This will obviously fail, as Django only uses the "app1" part as a
table prefix. I can fix that by distinquishing the models using
"app_label", but are there other areas in Django that rely on applications
having unique names? Do I need to ditch the Python-style namespacing
and resort to module1_app1, module2_app1 application names?
Cheers,
Marcus
--
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.
