Django not create database table

Question

Hey, I've a database already created. Now I've updated UserProfile with:

class UserProfile(models.Model):
    user = models.ForeignKey(User, unique = True, related_name = 'user')
    follows = models.ManyToManyField("self", related_name = 'follows') <-- NEW LINE

so python manage.py sqlall myapp returns me:

[...]
CREATE TABLE "myapp_userprofile_follows" (
    "id" integer NOT NULL PRIMARY KEY,
    "from_userprofile_id" integer NOT NULL,
    "to_userprofile_id" integer NOT NULL,
    UNIQUE ("from_userprofile_id", "to_userprofile_id")
)
[...]

When I run python manage.py syncdb:

Creating tables ...
Installing custom SQL ...
Installing indexes ...
No fixtures found.

But the table is not created when I try to insert data into. Why? (I'm testing locally, with sqlite3)

See stackoverflow.com/a/27204663/847501

Rafiq
– Rafiq

2014-11-29 17:31:01 +00:00
Commented Nov 29, 2014 at 17:31 — Rafiq
– Rafiq, Commented Nov 29, 2014 at 17:31

bradley.ayers · Accepted Answer · 2011-06-01 22:52:33Z

6

manage.py syncdb will not modify existing tables to add or remove fields. You will need to either manually modify your database, or use a tool like South to create automated database migrations (which is what I highly recommend)

answered Jun 1, 2011 at 22:52

bradley.ayers

38.5k14 gold badges98 silver badges101 bronze badges

Sign up to request clarification or add additional context in comments.

5 Comments

Fred Collins Over a year ago

ManyToManyField should create a new table, not add or delete column. Even with ManyToManyField should I us South?

Keegan Carruthers-Smith Over a year ago

He can also run manage.py reset myapp to just delete the tables and start with fresh data. Since he is adding a field which is not required, I think he can also run dumpdata to get a fixture, reset then load in the fixture.

bradley.ayers Over a year ago

@Fred, The way it works is that syncdb looks at the models in your project, then has a look in the database to see if that model's table already exists. If it does, it assumes everything about that model is already configured, this means that it doesn't even see the new ManyToManyField. So yes, even though adding a ManyToManyField will just create a new table, you will still need to use South for that (or modify the database yourself).

Fred Collins Over a year ago

Sure, I can create the tables manually, but how about indexes? Django create also indexes for the various table, in addition to tables. South manage this? By the way, I'll check it out in a while.

RedGlyph Over a year ago

From Django 1.4 site, "Creates the database tables for all apps in INSTALLED_APPS whose tables have not already been created.". It should create the table but indeed doesn't always do so, it's probably a bug in 1.4 (never seen this in 1.3), which version was this about? Anyway, as Keegan mentioned, manage.py reset myapp recreates correctly the tables though. Sadly enough, Django is really lacking in that domain...

Timmy O'Mahony · Accepted Answer · 2011-06-01 22:53:34Z

5

have you added your app to INSTALLED_APPS in settings.pys:

settings.py

INSTALLED_APPS = (
    ... ,
    'my_app',
)

https://docs.djangoproject.com/en/dev/ref/settings/?from=olddocs#installed-apps

answered Jun 1, 2011 at 22:53

Timmy O'Mahony

54.1k19 gold badges160 silver badges182 bronze badges

1 Comment

Timmy O'Mahony Over a year ago

Well I suppose I should have just figured that out. Very sorry for trying to help

Collectives™ on Stack Overflow

Django not create database table

2 Answers 2

5 Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

5 Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related