Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Suggestion/answer:</p> <p>I got some weird behaviour on that also! Because I was forgetting to add the 'LocaleMiddleware', double check if it is there, for illustration this is how my 'MIDDLEWARE_CLASSES' looks like:</p> <pre><code>MIDDLEWARE_CLASSES = ( 'django.middleware.common.CommonMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', ) </code></pre> <p>That Middleware is responsible for process your request and response, and add the language!</p> <p>Also keep the code from 'Sindri Guðmundsson', which is changing right the lang!</p> <p><strong>EDIT</strong></p> <p>A little bit further! If we take a look at LocaleMiddleware:</p> <pre><code>def process_request(self, request): language = translation.get_language_from_request(request) translation.activate(language) request.LANGUAGE_CODE = translation.get_language() </code></pre> <p>So the question is! why Django needs that?! the answer: Because if you use {{ LANGUAGE_CODE }} it is reading from the REQUEST, so LANGUAGE_CODE must be in the request! otherwise ! it is not going to return it! so thats why this middleware exist! Check it out the comment, in the actual source code of the middleware:</p> <pre><code>""" This is a very simple middleware that parses a request and decides what translation object to install in the current thread context. This allows pages to be dynamically translated to the language the user desires (if the language is available, of course). """ </code></pre> <p>Also check the docs: <a href="https://docs.djangoproject.com/en/1.3/topics/i18n/deployment/#how-django-discovers-language-preference" rel="nofollow">https://docs.djangoproject.com/en/1.3/topics/i18n/deployment/#how-django-discovers-language-preference</a></p>
    singulars
    1. This table or related slice is empty.
    1. POHow does django locale work between views
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USArthur Neves
    1. USArthur Neves
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow does django locale work between views
      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. VTBountyClose
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYou are absolutely correct - i removed that middleware cause if i remember correctly system started throwing some messages when i had it in middleware classes along with django dms multilingual url middleware.
      singulars
      1. PO
      1. USOdif Yltsaeb
    2. COSo, just put it back, and check if it works! if it does, i will be glad to here it from u =)
      singulars
      1. PO
      1. USArthur Neves
    3. COThing is - i dont want it and the question was - why do i need such middleware and why does it not just work by setting that cookie. But from Simons answer and remotely from yours it looks like one needs a middleware to do this for each and every request and thats how django works.
      singulars
      1. PO
      1. USOdif Yltsaeb
 

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