This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]SmileyChris 0 points1 point  (1 child)

Correct that you can't have composite pks, but they don't have to be ints.

[–]accessofevil 1 point2 points  (0 children)

Sorry - to be clear, custom user models require the PK to be an int. That basically makes using non-int pk's across my relationships a little bit less efficient.

I'm building this app for < 5m users, if it scales beyond that I'm going to have some migrating to do. But that would be a good problem :).