I poked around a little, and it looks like MySQL actually does support foreign keys across databases.
I guess my questions are: As long as the separate databases are not explicitly distributed eg. to different machines or different CPUs, is there any disadvantage to joining or constraining across database boundaries? And/or is there a good way for me to customize the names of the tables created by eg., auth, to dampen my urge to use a different database just for the sake of namespace hygiene? (I'm thinking that the answer to this is "no".) Thanks Alex On Nov 1, 7:58 am, Scott Gould <zinck...@gmail.com> wrote: > > If not, I could create a new database, and devote it to the django > > stuff. Is that a good solution? Are there significant disadvantages to > > using a separate mysql database just for the django stuff? Is there > > maintenance overhead for the dba? (I don't know.) Are there any > > disadvantages, say, to doing trans-database joins, or having trans- > > database key constraints, vs. within a single database? > > I am not a database expert -- only know enough to get by -- but as far > as I am aware MySQL does not support foreign keys across databases. > That is, you can put the auth system anywhere you like, but anything > that references the auth models will need to be in the same database, > directly or indirectly. Very likely a road you don't want to walk down. -- 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.
