@Jacob Thanks for all the links. I appreciate your reply.
Michael
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to
On Fri, Feb 26, 2010 at 5:17 PM, Jacob Kaplan-Moss wrote:
> There are many, and we've discussed this issue at length any number of
> times over the years. Please take the time to read over the history
> here; if you've got something new to add to the discussion I'd love to
>
On Fri, Feb 26, 2010 at 5:11 PM, orokusaki wrote:
> Well, I won't even try to argue with that, but there has to be a way
> to conquer problems like this in Django without editing the source
> code, don't you think?
There are many, and we've discussed this issue at
@James
Well, I won't even try to argue with that, but there has to be a way
to conquer problems like this in Django without editing the source
code, don't you think?
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group,
On Fri, Feb 26, 2010 at 3:26 PM, orokusaki wrote:
> 1) Allow for subclasses of normal models to override attributes of the
> parent model. Then, if any attributes exists that override the parent,
> simply use the subclass to create the table and treat the parent as an
>
Problem that exists:
1) I need to subclass `contrib.auth.User` and strip some of the
elements from it, like making `User.username` non-unique for SAAS with
multiple accounts (`MyCustomUser.username` would only be
`unique_together = ('account', 'username')`
(other instances could occur but I