makemigrations, migrate, and existing databases

Using Django Getting Started
21

however there is something that must be transferred to the database anyway.
Reading Writing your first Django app, part 2 | Django documentation | Django it is explained, talking about applications (optional but we might want it) :

Some of these applications make use of at least one database table, though, so we need to create the tables in the database before we can use them. To do that, run the following command:

$ python manage.py migrate

So, Are we suppose, in the case that we have a database already set up, and we want to use for example
django.contrib.admin or auth to make te tables by hand ? (I guess ti is explained somewhere but …) , because it well mantioned in the Intégration de Django avec une base de données existante | Documentation de Django | Django (that I had read long time ago, sorry I might have done it again) that we should use migrate anyway.

How can I change the title of this thread (to something like : about migrate, mkmigrations and existing databases )

22

In my previous reply, referencing the use of makemigrations and migrate with existing data:

So yes, you generally want to use migrate anytime you’re starting a project, precisely because of those system tables that need to be defined.

  • You should see a “pencil” icon next to the title at the beginning of the thread. That allows you to change the title and the category in which this thread is placed.
  • I’ve gone ahead and changed it for you.
23

thanks a lot for all.