Hi All,
I'm currently working on an authentication backend that adds some
functionality to the standard one, and as part of this I want to modify
the behaviour of the User class. I've been subclassing auth.models.User
using standard model inheritance and it seems to be working fine.
However, I don't need to add any fields to the User class, just
add/modify some methods. It seems like a waste to have an additional
database table created for my model subclass when it won't contain any
useful information. I briefly toyed with the idea of just
monkey-patching the User class, but figured there must be a better
way :-)
So, is there a way to have a model subclass avoid the creation of a
new database table,and just take its data straight out of the table for
its superclass?
Thanks,
Ryan
--
Ryan Kelly
http://www.rfk.id.au | This message is digitally signed. Please visit
r...@rfk.id.au | http://www.rfk.id.au/ramblings/gpg/ for details
signature.asc
Description: This is a digitally signed message part
