In addition, I think if you duplicate the existing auth app under another name, you're not going to be able to use the django.contrib applications, since lots of those (like admin) count on being able to do database joins between their table and the existing auth app's model objects.
In other words, if you're trying to use session, admin, and so forth, tweaking the existing auth app might work, but I don't think duplicating it will work. Not an expert but just spent some time working through this stuff, Leo On Oct 2, 9:38 am, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > On 10/2/07, handsome greg <[EMAIL PROTECTED]> wrote: > > Short version - you can't do what you describe. The database tables > for the contrib.auth app aren't customizable, so you're not going to > be able to point them at your own database without duplicating the > existing auth app, or tweaking the existing one. > > Yours, > Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
