django no such table:

Question

I have models in Django set up as below.

class Pupil(models.Model):
    forename = models.CharField(max_length=30)
    surname = models.CharField(max_length=30)
    dateofbirth = models.DateField()
    year = models.IntegerField()
    class_group = models.CharField(max_length=30)
    email = models.EmailField(blank=True)
    assignments = models.ManyToManyField('Assignment', verbose_name='related assignments')

    def __unicode__(self):
        return u'%s %s' % (self.forename, self.surname)

class Subject(models.Model):
    name = models.CharField(max_length=30)
    level = models.CharField(max_length=30)
    teachers = models.ManyToManyField('Teacher', verbose_name='related teachers')

    def __unicode__(self):
        return self.name

class Teacher(models.Model):
    forename = models.CharField(max_length=30)
    surname = models.CharField(max_length=30)
    email = models.EmailField(blank=True)

    def __unicode__(self):
        return u'%s %s' % (self.forename, self.surname)

class Assignment(models.Model):
    assignment_name = models.CharField(max_length=30)
    date_assigned = models.DateField()
    date_submitted = models.DateField()

    def __unicode__(self):
        return self.assignment_name

When I attempt to add a pupil and attach an assignment to the pupil in the admin, I get a database error -

no such table: homework_pupil_assignments

after reading this I realised this could be due to django not updating changes to my models as when I do manage.py sqlall homework

I see the following:

BEGIN;
CREATE TABLE "homework_pupil_assignments" (
    "id" integer NOT NULL PRIMARY KEY,
    "pupil_id" integer NOT NULL,
    "assignment_id" integer NOT NULL,
    UNIQUE ("pupil_id", "assignment_id")
)
;
CREATE TABLE "homework_pupil" (
    "id" integer NOT NULL PRIMARY KEY,
    "forename" varchar(30) NOT NULL,
    "surname" varchar(30) NOT NULL,
    "dateofbirth" date NOT NULL,
    "year" integer NOT NULL,
    "class_group" varchar(30) NOT NULL,
    "email" varchar(75) NOT NULL
)
;
CREATE TABLE "homework_subject_teachers" (
    "id" integer NOT NULL PRIMARY KEY,
    "subject_id" integer NOT NULL,
    "teacher_id" integer NOT NULL,
    UNIQUE ("subject_id", "teacher_id")
)
;
CREATE TABLE "homework_subject" (
    "id" integer NOT NULL PRIMARY KEY,
    "name" varchar(30) NOT NULL,
    "level" varchar(30) NOT NULL
)
;
CREATE TABLE "homework_teacher" (
    "id" integer NOT NULL PRIMARY KEY,
    "forename" varchar(30) NOT NULL,
    "surname" varchar(30) NOT NULL,
    "email" varchar(75) NOT NULL
)
;
CREATE TABLE "homework_assignment" (
    "id" integer NOT NULL PRIMARY KEY,
    "assignment_name" varchar(30) NOT NULL,
    "date_assigned" date NOT NULL,
    "date_submitted" date NOT NULL
)
;
COMMIT;

I then installed South, following the directions to get up and running with an existing app, in the hope of successfully syncing these tables. No joy.

Can anyone suggest how I can get the database (sqlite3) to reflect the models or point out what I'm doing wrong?

did you do a `convert_to_south app_name` before you did `schemamigration` ? — karthikr, Oct 08 '12 at 15:35
Yup. I'm also concerned that if the tables were not synced properly before the integration of South, it'll cause a problem. — puffin, Oct 08 '12 at 15:41
check in the south_migrationhistory table, and see if this migration is executed or not — karthikr, Oct 08 '12 at 15:43
You should back out your changes to the point where they match what the database looks like, then do the schemamigration --initial. At that point, you should add your changes back in, do another schemamigration --auto and then a migrate — James R, Oct 08 '12 at 15:51

score 134 · Accepted Answer · edited Nov 22 '18 at 04:46

Updated answer for Django migrations without `south` plugin:

Like T.T suggested in his answer, my previous answer was for south migration plugin, when Django hasn't any schema migration features. Now (works in Django 1.9+):

T.T wrote:

You can try this!

python manage.py makemigrations

python manage.py migrate --run-syncdb

Outdated for `south` migrations plugin

As I can see you done it all in wrong order, to fix it up your should complete this checklist (I assume you can't delete sqlite3 database file to start over):

Grab any SQLite GUI tool (i.e. http://sqliteadmin.orbmu2k.de/)

Change your model definition to match database definition (best approach is to comment new fields)

Delete migrations folder in your model

Delete rows in south_migrationhistory table where app_name match your application name (probably homework)

Invoke: ./manage.py schemamigration <app_name> --initial

Create tables by ./manage.py migrate <app_name> --fake (--fake will skip SQL execute because table already exists in your database)

Make changes to your app's model

Invoke ./manage.py schemamigration <app_name> --auto

Then apply changes to database: ./manage.py migrate <app_name>

Steps 7,8,9 repeat whenever your model needs any changes.

I have dropped all the tables from the shell. I then sync'd and migrated and it seems to have worked. — puffin, Oct 08 '12 at 19:14
This does not work in Django 1.8.7 as schemamigration is no longer defined as a subcommand for manage.py — CodeMonkey, Jan 21 '16 at 22:42

score 97 · Answer 2 · edited Aug 19 '16 at 10:20

97

You can try this!

python manage.py migrate --run-syncdb

I have the same problem with Django 1.9 and 1.10. This code works!

edited Aug 19 '16 at 10:20

Marcin Koziński

10,835
3
47
61

answered Aug 19 '16 at 03:35

T.T

1,011
1
7
6

score 13 · Answer 3 · edited Nov 22 '18 at 04:41

13

If you are using latest version of django 2.x or 1.11.x then you have to first create migrations ,

python manage.py makemigrations

After that you just have to run migrate command for syncing database .

python manage.py migrate --run-syncdb

These will sync your database and python models and also second command will print all sql behind it.

edited Nov 22 '18 at 04:41

Srinivas Reddy Thatiparthy

10,985
4
45
68

answered Nov 21 '17 at 08:57

Shubham Sharma

2,763
5
31
46

1

`python manage.py migrate --run-syncdb` was also working for me with django `3.0` – Moritz Mar 19 '20 at 20:50

score 4 · Answer 4 · edited Jul 06 '20 at 21:51

4

. first step delete db.sqlite3 file . go to terminal and run commands:

python manage.py makemigrations
python manage.py migrate
python manage.py createsuperuser
python manage.py runserver . go to admin page every thing ok now.

edited Jul 06 '20 at 21:51

Laurent LAPORTE

21,958
6
58
103

answered Jul 06 '20 at 19:37

Raf

49
1

This was what fixed it for me. I had to delete the db.sqlite3 file first. Thank you – SkinnyPigeon Jan 21 '22 at 23:10

score 3 · Answer 5 · edited Apr 15 '19 at 12:55

3

I think maybe you can try

python manage.py syncdb

Even sqlite3 need syncdb

sencondly, you can check your sql file name

it should look like xxx.s3db

edited Apr 15 '19 at 12:55

ketimaBU

901
4
15
35

answered Aug 10 '13 at 16:46

creepyuncle

56
2

score 3 · Answer 6 · answered Sep 19 '18 at 07:49

One way to sync your database to your django models is to delete your database file and run makemigrations and migrate commands again. This will reflect your django models structure to your database from scratch. Although, make sure to backup your database file before deleting in case you need your records.

This solution worked for me since I wasn't much bothered about the data and just wanted my db and models structure to sync up.

score 2 · Answer 7 · answered Oct 08 '12 at 16:05

2

sqlall just prints the SQL, it doesn't execute it. syncdb will create tables that aren't already created, but it won't modify existing tables.

answered Oct 08 '12 at 16:05

Daniel Roseman

588,541
66
880
895

1

Actually syncdb is no longer supported in the newer versions of Django and therefore this answer is wrong. – Benyamin Noori Sep 23 '15 at 13:25

score 1 · Answer 8 · edited Mar 23 '21 at 00:42

1

(1) delete -> db.sqlite3
(2) your App -> migrations directory-> delete all 001_initial.py and others but dont delete __init__.py

(3) open terminal -> 
python manage.py makemigrations
python manage.py migrate

edited Mar 23 '21 at 00:42

desertnaut

57,590
26
140
166

answered Mar 21 '21 at 23:41

Ugur hmz

21
1

3

This works, but be aware that it will delete your database! – ddulaney Mar 22 '21 at 03:44

score 0 · Answer 9 · answered May 04 '21 at 10:26

0

First run: python manage.py makemigrations
Second run: python manage.py migrate

answered May 04 '21 at 10:26

Himaloy Mondal

127
2
6

django no such table:

9 Answers9

Updated answer for Django migrations without `south` plugin:

Outdated for `south` migrations plugin

Linked

django no such table:

9 Answers9

Updated answer for Django migrations without south plugin:

Outdated for south migrations plugin

Linked

Updated answer for Django migrations without `south` plugin:

Outdated for `south` migrations plugin