Changes between Initial Version and Version 1 of Ticket #13691, comment 7


Ignore:
Timestamp:
02/18/2011 04:19:13 PM (4 years ago)
Author:
wwinham
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #13691, comment 7

    initial v1  
    1 Just as a reference for anyone coming here with this error from google, a possible cause here was the use of sqlite with a relative path for the DATABASE_NAME field. In that case, running manage.py syncdb in a different directory from where you run manage.py runserver could give you that error because you're actually using different databases. I hadn't used sqlite with django in a while, so I just ran in to that.
     1Just as a reference for anyone coming here with this error from google, a possible cause is the use of sqlite with a relative path for the DATABASE_NAME field. In that case, running manage.py syncdb in a different directory from where you run manage.py runserver could give you that error because you're actually using different databases. I hadn't used sqlite with django in a while, so I just ran in to that.
    22
    3 A hardcode path for the DATABASE_NAME solves this.
     3A full, non-relative path for the DATABASE_NAME solves this.
Back to Top