On Mon, Sep 22, 2008 at 11:39 AM, HenrikV <[EMAIL PROTECTED]>wrote:
>
> I hope your reply was helpful to others. I asked a question because I
> am not as knowledgeable about Django internals as you obviously are,
> and this is this is to my knowledge the place to ask.
> I make no assumptions about
I hope your reply was helpful to others. I asked a question because I
am not as knowledgeable about Django internals as you obviously are,
and this is this is to my knowledge the place to ask.
I make no assumptions about where there is a bug, or if there is one,
as I haven't figured out how things
On Sat, Sep 20, 2008 at 6:13 PM, HenrikV <[EMAIL PROTECTED]> wrote:
>
> I am working on #3011, making the User model overridable.
Ok - do you think this might have been useful information to include
on your original query?
> I have a
> working patch, but
> if I set the db_table on the User model
I am working on #3011, making the User model overridable. I have a
working patch, but
if I set the db_table on the User model, the queryset and syncdb
doesn't seem to agree
on what the m2m table should be called.
As a sidenote there seems to a problem with certain combinations
db_table and app_na
On Sat, Sep 20, 2008 at 2:47 AM, HenrikV <[EMAIL PROTECTED]> wrote:
>
> If you imagine changing the table name of the auth.User table to
> 'account_user'. Should the groups relationship create a table called
> 'account_user_groups' or 'auth_user_groups' ?
I'm unclear if this is a user 'how to' qu
If you imagine changing the table name of the auth.User table to
'account_user'. Should the groups relationship create a table called
'account_user_groups' or 'auth_user_groups' ?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Goog
