User Isolation between sites.

[jorgeecardona]

I want to add a feature in which the users can be isolated between sites, in order to improve multitenancy in django.

I added to auth.User a site field as ForeignKey with null=True and default=None, and in Meta a unique_together=('name', 'site'). The actual tests run without problem with that.

I will add more tests soon.

Ref:

​http://code.djangoproject.com/ticket/15089

[jorgeecardona]

Add a site field in user with null=True and default=None, and a new constraint for uniquness between username and site.

[jorgeecardona]

I changed the create_user method in UserManager in order to receive a site object, and also made some testes for integrity error.

[jorgeecardona]

Modify create_user and unit test.

[Ramiro Morales]

The problem with a change like this (similarly to other proposals made before to change the schema of often used contrib.* apps models) is that it will mean everybody will need to manually modifiy the structure of the DB table(s) associated with the modified model(s).

Moving to the 2.0 milestone, when it hopefully will be worth considering all these backward incompatible changes.

[James Addison]

Somewhat related to #15089.

[Jacob]

Milestone 2.0 deleted

[Aymeric Augustin]

Change UI/UX from NULL to False.

[Aymeric Augustin]

Change Easy pickings from NULL to False.

[Aymeric Augustin]

Isn't this problem essentially solved by the custom user models introduced in Django 1.5?

[Anssi Kääriäinen]

For the usermodel.site field: yes.

I don't think we want to drag this ticket into solving all possible problems when having multiple users with same username, but different site. If there are places which makes this usecase extra complicated lets consider fixing those in separate tickets.

So, closing this as fixed (by custom user models).