Re: table namespace hygiene: should I try to rename auth_* tables, or should I use a separate database?

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