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. The convention Django uses is a DB for the project and <appname>_<modelname> for the tables. This should not prevent any conflicts since a Python error would occur if you duplicated a model within your app's model. I am not aware of any MySQL limit on tables per DB, nor should it make a difference from a performance perspective. Just keep in mind that these apps will all share a single admin interface, and while there are some access controls, they may not be granular enough for what you need. That may drive your requirement to move some of these apps to a separate project. On Sep 6, 4:27 pm, "Adam Jenkins" <[EMAIL PROTECTED]> wrote: > 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 issue, or > are there any other problems I should look out for? > > -- > --------------------------------------- > Adam Jenkins > [EMAIL PROTECTED] > 312-399-5161 > --------------------------------------- --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
