I agree with you Shai, that's why I proposed a command that makes use of
migrations internals (not to use a migration per se) to do the job.
Thanks for the feedback Marc, I know having the migration to use django orm
is a much slower process than importing it from a textual source, but the
main
I'd suggest your approach is also quite slow. Andrew Godwin did something
similar once at a lower level - see
https://github.com/lanyrd/mysql-postgresql-converter (use at your own risk)
On 10 June 2016 at 19:44, Bruno Ribeiro da Silva
wrote:
> The problem here is that
Hey guys, I'm not sure if I should be asking this here, but it's related to
django internals.
I have this idea to create a command that uses the migrations api to
migrate all the data from one database (eg. MySQL) to another database
(PostgreSQL).
So I would run the migrations in the new