| | 1 | 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. |
| | 2 | |
| | 3 | This 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.) |
| | 4 | |
| | 5 | Some of these may seem like quick patches but I know that others will take a bit of consideration -- that's why the wiki page rather than individual tickets. |
| | 6 | |
| | 7 | For now, let's try dividing them into sections by major module. Within those sections suggested format is: error message, explanatory context (often important -- a message that is very helpful in one context can be confusing in another), suggested improvements/changes. |
| | 8 | |
| | 9 | |
| | 10 | == django.db == |
| | 11 | |
| | 12 | {{{ |
| | 13 | django.core.exceptions.ImproperlyConfigured: Could not load database backend: cannot import name connection. |
| | 14 | Is your DATABASE_ENGINE setting (currently, 'mysql') spelled correctly? |
| | 15 | Available options are: 'ado_mssql', 'dummy', 'mysql', 'postgresql', 'sqlite3' |
| | 16 | }}} |
| | 17 | '''Context:''' I encountered this while hacking on the db backend, which means its possibly very obscure.[[BR]] |
| | 18 | '''Suggestion:''': Django can determine whether the DATABASE_ENGINE setting is valid; it doesn't need to ask. |