Am Sonntag, 13. Mai 2012 23:17:15 UTC schrieb Russell Keith-Magee: > However, the big catch -- Django's concept of a "User" isn't > especially easy to customise. This means that won't be trivial > (possible, but not trivial, and certainly not documented) to use your > legacy table as a substitute for Django's internal User table. This > means that you won't be able to use any existing applications out > there that have a foreign key on Django's User - most notably, > Django's admin interface. > > Depending on your exact needs, one easy workaround for this may be to > have 2 user tables: the legacy user table, and an 'administrators' > user table. The legacy users will still be able to log in, but won't > have access Django's admin. The admin Users table is Django's own User > table, and users with accounts on this table will have access to the > Django admin, including the ability to view/edit the legacy User > table. > Thanks for your answer, Russ. It seems, in this particualar case, there would be more fighting against Django than profiting from the things it offers. I think I'll implement the user management app some other way and look for something to make my first Django app where Django will really help me get things done.
Thanks, Peter -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/clIosFIinZAJ. To post to this group, send email to django-users@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.
