Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#23393 closed Bug (invalid)

"Table does not exist" error running tutorial under 1.7rc3

Reported by: Russell Keith-Magee Owned by: nobody
Component: Core (Management commands) Version: 1.7-rc-3
Severity: Release blocker Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


Logging this as a placeholder; it's possible this might not be a problem, but two people got it independently during the Django tutorial at DjangoCon US.

The first time you run " run server" in the tutorial, you should get the "congratulations, it worked" page. However, unless you run syncdb, you get a nasty stack trace complaining about the absence of the sessions table.

Change History (2)

comment:1 Changed 6 years ago by Tim Graham

Resolution: invalid
Status: newclosed

The order was switched in 6923fdbbf1824d6e28cc1d283b48146c7f58c6ea to make sure the database is migrated first, so I don't think it's an issue.

comment:2 Changed 6 years ago by Collin Anderson

Ok, so you must migrate before using runserver for the first time.

Note: See TracTickets for help on using tickets.
Back to Top