On 12/04/2018 12:44 PM, tango ward wrote:
Sorry for the follow up question, when you say run migration locally,
this is running python manage.py makemigrations and python manage.py
migrate, right? Please let me know if I got these steps correctly:
- make a postgres test db
- changed database
Sorry for the follow up question, when you say run migration locally, this
is running python manage.py makemigrations and python manage.py migrate,
right? Please let me know if I got these steps correctly:
- make a postgres test db
- changed database settings in settings.py and point it to test d
At the moment, I am comparing the fields from the dump file and the fields
in our models.py. There are fields that exist on the dump file that are not
yet in our existing model/models that why I want to know if should I modify
the schema of our database to match the dump file of the client. I'm los
On 12/04/2018 9:47 AM, tango ward wrote:
Hi Mike,
Thanks for the advice.
May I ask as well, on Django side, since we have already an existing
system, how should I adjust the fields that are existing from the dump
file to the Django? Should I just add fields in models.py?
Treat that as a se
On 11/04/2018 11:40 PM, tango ward wrote:
Hi there,
This will be my first time to migrate a database in my first
programming job. I checked the dump file today and load it in MySQL
benchmark to view the ERD. The database that I need to migrate has 48
tables and has existing data already.
I
Hi there,
This will be my first time to migrate a database in my first programming
job. I checked the dump file today and load it in MySQL benchmark to view
the ERD. The database that I need to migrate has 48 tables and has existing
data already.
I would like to know what are the things that I n
6 matches
Mail list logo
