#30706: Why isn't the auth.User.id field documented?
               Reporter:  Conrad     |          Owner:  nobody
                   Type:             |         Status:  new
  Cleanup/optimization               |
              Component:             |        Version:  2.2
  Documentation                      |
               Severity:  Normal     |       Keywords:  auth Documentation
           Triage Stage:             |      Has patch:  0
  Unreviewed                         |
    Needs documentation:  0          |    Needs tests:  0
Patch needs improvement:  0          |  Easy pickings:  0
                  UI/UX:  0          |
 I asked this at the GitHub project
 ([https://github.com/django/djangoproject.com/issues/934]) and was
 redirected here: the default Django User id field exists and is used a lot
 (as far as questions on Stack Overflow and example projects I can find
 go), but I can't find any documentation on it apart from the fact, that it
 is set "None" for Anonymous Users. @frankwiles told me on GitHub that the
 reason might be that all models have the "id" field by default, but I
 couldn't find a source that this is the reason why it isn't mentioned in
 the docs.

 I believe it is ok to use it, if not it should be added to the
 documentation as a warning or similar text. If it is ok to use it, why not
 write it down? It would help people like me (pretty new to Django) to
 quickly find how to use unique user ids, maybe there are even some custom
 settings most people don't know about.

Ticket URL: <https://code.djangoproject.com/ticket/30706>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Reply via email to