I understand that Django handles database creation using migrations files and that any changes to the table are carried out using ALTER statements in a new migration file.
My question isn't django specific:
Would an initial CREATE followed by multiple ALTER operations on a table affect the performance of the table in any way? What if data was inserted in the intermediate stages?
Would it be better to do a dump of the latest schema and data and execute a single CREATE instead?
I initially thought that it would be better to not commit migrations to github since they're derived from the models.py files anyway. Now i realize that standard practice is to keep updating the migrations on github. Is there any reason this method is preferred to running makemigrations with the updated model files?