Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>In most cases this means that the <strong>previous</strong> SQL statement failed to execute. In this case you should:</p> <ol> <li><p><strong>Enable SQL <a href="https://docs.djangoproject.com/en/dev/topics/logging/#id1">logging</a></strong>, see the following snippet to paste in settings.py</p></li> <li><p><strong>Set DEBUG=1</strong>, or SQL won't be logged</p></li> <li><p><strong>Run runserver again</strong>, and you should see all SQL queries in the console</p></li> <li><p><strong>Execute the last SQL queries directly in your database</strong>, you should then find which queries fail and then you should be able to debug them - or open a new question which is specific to the query that causes the problem. You can use phpMyAdmin, or directly a CLI client, or whatever database client, to execute the SQL queries one by one until you find the one that needs some love.</p></li> </ol> <p>SQL Logging configuration:</p> <pre><code>LOGGING = { 'version': 1, 'disable_existing_loggers': True, 'formatters': { 'simple': { 'format': '%(levelname)s %(message)s', }, }, 'handlers': { 'console':{ 'level':'DEBUG', 'class':'logging.StreamHandler', 'formatter': 'simple' }, }, 'loggers': { 'django': { 'handlers': ['console'], 'level': 'DEBUG', }, } } </code></pre> <p>If this configuration does not provide any additional console output with <code>runserver</code>, then feel free to try <a href="http://django-autocomplete-light.readthedocs.org/en/latest/demo.html">django-autocomplete-light's example test_project</a>:</p> <ol> <li><p>Read and paste the installation commands in <code>/tmp</code></p></li> <li><p>Change dir to <code>autocomplete_light_env/src/django-autocomplete-light/test_project</code></p></li> <li><p>Open <code>test_project/settings.py</code>, replace the <code>LOGGING</code> configuration by the one above</p></li> <li><p>Runserver and open your browser</p></li> </ol> <p>Your console will look like:</p> <pre><code>Validating models... 0 errors found Django version 1.4.1, using settings 'test_project.settings' Development server is running at http://127.0.0.1:8000/ Quit the server with CONTROL-C. DEBUG (0.001) SELECT "django_content_type"."id", "django_content_type"."name", "django_content_type"."app_label", "django_content_type"."model" FROM "django_content_type" WHERE ("django_content_type"."model" = taggable AND "django_content_type"."app_label" = charfield_autocomplete ); args=('taggable', 'charfield_autocomplete') DEBUG (0.000) SELECT DISTINCT "tagging_tag".id, "tagging_tag".name FROM "tagging_tag" INNER JOIN "tagging_taggeditem" ON "tagging_tag".id = "tagging_taggeditem".tag_id INNER JOIN "charfield_autocomplete_taggable" ON "tagging_taggeditem".object_id = "charfield_autocomplete_taggable"."id" WHERE "tagging_taggeditem".content_type_id = 11 GROUP BY "tagging_tag".id, "tagging_tag".name ORDER BY "tagging_tag".name ASC; args=[] </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POHow to debug: Internal Error current transaction is aborted, commands ignored until end of transaction block
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USjpic
    1. USjpic
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to debug: Internal Error current transaction is aborted, commands ignored until end of transaction block
      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. VTAcceptedByOriginator
    1. COYour suggested SQL logging configuration does not provide any addition console logging for me. I have DEBUG = True, so I'm not sure what else to try to actually see the SQL. I had an error in my .extra() call, my where had a typo. Took me several hours to notice it. Would have been a piece of cake had I been able to see the SQL I was generating. I got my issue fixed, but Django was sure no help.
      singulars
      1. PO
      1. USgdonald
    2. COI am giving +1 to your answer, because of "In most cases this means that the previous SQL statement failed to execute." was exactly the case for my issue. The stack trace showed an object failing to save, but it was actually a query above it. It's been my experience that Django stack traces are not helpful at all in most cases.
      singulars
      1. PO
      1. USgdonald
    3. COI'm preoccupied by "does not provide **any additional** console logging". So i updated the answer to include an easy way to test this LOGGING configuration. This allows you to know if this comes frob your project (settings?) or environment.
      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