Commit 73168816 authored by BERJON Matthieu's avatar BERJON Matthieu
Browse files

Add of a README file



I added a README file in order to document the process of mapping a
current legacy database with Django. It's required only at the start of
the project or creation of a new app calling a legacy database. This
helps to start the historic of the migrations to the current state of
the database.
Signed-off-by: BERJON Matthieu's avatarMatthieu Berjon <matthieu.berjon@inria.fr>

Update the of README file

I updated the documentation to precise the fact that the migration
process must be applied for each app calling the legacy database.
Signed-off-by: BERJON Matthieu's avatarMatthieu Berjon <matthieu.berjon@inria.fr>
parent 6ad4925e
Installation
============
Warning, because we use a legacy database, Django can't deal with it because
it doesn't have the history of the previous migrations. This process must be
applied each time that you create a new app calling a legacy database. The
following process must be applied:
.. bash
# load the database
mysql -u root -h localhost < dump.sql
# Tell Django the to start the migration at this stage of the database
python manage.py makemigrations <app_label>
# Create the migrations
python manage.py migrate --fake-initial
From that point, you can add the any required fields and process to the
migrations as usual.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment