api_notebook.user_id field is shorter than the referenced field about boomerang HOT 4 CLOSED

https://stackoverflow.com/questions/45911440/why-does-django-set-a-shorter-maximum-length-of-foreign-keys-to-auth-user-userna

from boomerang.

I think the reason for this behavior is the undocumented swappable property of the User model. It is designed to be replaceable by custom models. However, the configured model must have its data in the initial migration of the app that defines the model. The migrations code seems to generate references to the initial migration of swappable models. I am using the default User model, and its initial migration sets the username to 30 chars. Hence my username FKs are 30 chars long. I am able to work around this with a RunSQL migration to alter the FK data type to varchar(15), but I am in doubt if it's the right thing to do.

from boomerang.

It is left to explain how the populate script worked before. It is possible that it worked at a time when user child objects referred to users by id instead of username and joins were performed to handle user child requests.

from boomerang.

Leaving it as it is for now. Added commit 789d73c with a note about a known bug, a fix for the populator and a potential migration as a workaround that can be applied later.

from boomerang.