On 9/6/07, Adam Jenkins <[EMAIL PROTECTED]> wrote:
> This actually brings up an issue. I've heard that many Django developers
> don't
> use projects at all, that they just use apps. Is this correct? Should I
> default to one
> project and break it up into smaller ones if the need arises?
First
Possibly. I have never heard of this and I do not do it. If I were
just making random applications for distribution to others I might
consider it, but most of the time I am making an application for a
specific purpose or organization/company. In that case, I create a
project for the
On 9/6/07, Brian Morton <[EMAIL PROTECTED]> wrote:
>
>
> Well, by its nature, each Django project has its own DB. Multi-db
> support is coming soon, but not in trunk yet.
>
> If these are all applications that belong to the same project, Django
> is not designed to handle them on a per-DB basis.
I'm moving old php apps to Django. All the old php apps each have their own
DB. So I'm deciding now if I should just put everything inside a big DB. I
think when I'm all done, I could easily push 200 tables. Almost all of these
are intranet apps, so the load is pretty small. Is one large DB an
4 matches
Mail list logo
