Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Refs #14881 -- Document that User models need to have an integer prim…

…ary key.

Thanks to Kaloian Minkov for the reminder about this undocumented requirement.
  • Loading branch information...
commit 91c26eadc9b4efa5399ec0f6c84b56a3f8eb84f4 1 parent 87854b0
Russell Keith-Magee authored February 16, 2013

Showing 1 changed file with 4 additions and 2 deletions. Show diff stats Hide diff stats

  1. 6  docs/topics/auth/customizing.txt
6  docs/topics/auth/customizing.txt
@@ -466,11 +466,13 @@ Specifying a custom User model
466 466
 
467 467
 Django expects your custom User model to meet some minimum requirements.
468 468
 
469  
-1. Your model must have a single unique field that can be used for
  469
+1. Your model must have an integer primary key.
  470
+
  471
+2. Your model must have a single unique field that can be used for
470 472
    identification purposes. This can be a username, an email address,
471 473
    or any other unique attribute.
472 474
 
473  
-2. Your model must provide a way to address the user in a "short" and
  475
+3. Your model must provide a way to address the user in a "short" and
474 476
    "long" form. The most common interpretation of this would be to use
475 477
    the user's given name as the "short" identifier, and the user's full
476 478
    name as the "long" identifier. However, there are no constraints on

0 notes on commit 91c26ea

Please sign in to comment.
Something went wrong with that request. Please try again.