Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The django.contrib.auth.context_processors.auth sets the <code>{{ user }}</code> template context variable to either request.user or AnonymousUser. So, it overrides the <code>{{ user }}</code> context variable created by your DetailView:</p> <pre><code>def auth(request): """ Returns context variables required by apps that use Django's authentication system. If there is no 'user' attribute in the request, uses AnonymousUser (from django.contrib.auth). """ # If we access request.user, request.session is accessed, which results in # 'Vary: Cookie' being sent in every request that uses this context # processor, which can easily be every request on a site if # TEMPLATE_CONTEXT_PROCESSORS has this context processor added. This kills # the ability to cache. So, we carefully ensure these attributes are lazy. # We don't use django.utils.functional.lazy() for User, because that # requires knowing the class of the object we want to proxy, which could # break with custom auth backends. LazyObject is a less complete but more # flexible solution that is a good enough wrapper for 'User'. def get_user(): if hasattr(request, 'user'): return request.user else: from django.contrib.auth.models import AnonymousUser return AnonymousUser() return { 'user': SimpleLazyObject(get_user), 'messages': messages.get_messages(request), 'perms': lazy(lambda: PermWrapper(get_user()), PermWrapper)(), } </code></pre> <p>You can work around the issue by <a href="https://docs.djangoproject.com/en/dev/topics/class-based-views/#making-friendly-template-contexts" rel="noreferrer">setting context_object_name</a>. For example, this will enable the <code>{{ user_object }}</code> context variable, set to the user of the DetailView:</p> <pre><code>url( r'^users/(?P&lt;pk&gt;\d+)/$', DetailView.as_view( model = User, template_name = 'doors/users/detail.html', context_object_name = 'user_object' ), name = 'users_detail' ) </code></pre> <p>Dig deeper, read the documentation for <a href="https://docs.djangoproject.com/en/dev/ref/class-based-views/#django.views.generic.detail.SingleObjectMixin.get_context_object_name" rel="noreferrer">get_context_object_name()</a>.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to do a DetailView of Users in Django?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDaniel Kitachewsky
    1. USjpic
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to do a DetailView of Users in Django?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI'm not 100% sure on this, but I had other generic views, and the variable is the name of the model. For example, if I did `model = Poll` in a `ListView`, then the variable becomes `poll_list`. The same in a `DetailView` gives a variable name of `poll`. Maybe this is something new in Django v1.4?
      singulars
      1. PO
      1. UShobbes3
    2. COYou are correct, I fixed the above answer. Thank you for your feedback !
      singulars
      1. PO
      1. USjpic
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload