On 08/26/2015 12:18 PM, Marcin Nowak wrote:
>
> On 26 August 2015 at 20:09, Hugo Osvaldo Barrera <
hu...@barrera.io
> <mailto:
hu...@barrera.io>> wrote:
>
> Oh, so the field you're adding in monkey patching contrib.auth.User?
> IMHO, the design problem isn't django, but rather monkey-patching
> models itself. Maybe you'd be better of using a custom user model.
>
>
> I've tried to use custom user model, but Django forces me to change all
> FK`s. This is not possible for now.
>
> I need to add just one column / field to existing User model. Nothing
> more, nothing less.
>
> AFAIK I should create profile for user and put this column into profile
> model, but there are two disadvantages:
>
> * the profile is not necessary now and will contain just one column
> (well, three when incl. PK and FK to user)
> * performance issues (joining table)
>
> I think that for this use case "Custom user" will not work. I was wrong.
> I must forget about "Custom user". ;)
Yes. I think the most important Django limitation here is how difficult
it is to switch from built-in User to custom User. That's a real
problem, and it should be fixed (but at the moment I'm not sure how to
fix it).
Better support for monkeypatching is not very interesting.
Carl