Changes between Version 6 and Version 7 of BetterErrorMessages


Ignore:
Timestamp:
05/08/06 15:53:14 (9 years ago)
Author:
pb@…
Comment:

Added "OperationalError: Unable to close due to unfinalised statements"

Legend:

Unmodified
Added
Removed
Modified
  • BetterErrorMessages

    v6 v7  
    11= Better Error Messages =
    22
    3 Better error messages make everybody work faster. I'm starting this page as a place to collect error messages that could stand improvement, or which are misleading or confusing in certain contexts. Most of us have had the experience of getting a "weird" message, puzzling it out (perhaps with help from django-users or #django) and then moving on. Later it can be hard to remember what the problem was.
     3I'm starting this page as a place to collect error messages that could stand improvement, or which are misleading or confusing in certain contexts. Most of us have had the experience of getting a "weird" message, puzzling it out (perhaps with help from django-users or #django) and then moving on. Later it can be hard to remember what the problem was.
    44
    55This is an experiment to see if having a dedicated place to describe these cases as we encounter them can help organize a quality-control effort. Good error messages make for more productive developers. (And it helps newbies be more self-supporting, too.)
     
    2020'''Suggestion:''' Django can determine whether the DATABASE_ENGINE setting is valid; it doesn't need to ask.
    2121
     22{{{
     23OperationalError: Unable to close due to unfinalised statements
     24}}}
     25'''Context:''' SQLite file permissions are incorrect (directory or DB file lack write permission)[[BR]]
     26'''Suggestion:''' Check file permissions when running with SQLite backend and warn user if they seem incorrect
     27
    2228== django.contrib.admin ==
    2329
    2430Ticket #1732 -- a problem that elicits no error message, but should.
    2531
    26 Ticket #1808 -- omitting the "Admin" internal class in certain situations generates the message `'NoneType' object has no attribute 'get_field_sets'`
     32{{{
     33'NoneType' object has no attribute 'get_field_sets'
     34}}}
     35'''Context:''' One or more models that are referenced by ForeignKey from another model are missing their inner `Admin` class. Possible other causes as well. See ticket #1808. [[BR]]
     36'''Suggestion:''' Check relevant Admin settings during model validation?
    2737
    2838== django.core ==
Back to Top