I wouldn't recommend that
Migrations are tightly tied to your app as you need them to set you app up.
In that sense, they should be database agnostic, as your app is (because
Django is).
Using a migration that only works for MySQL seems very strange to me.
Indeed, such a migration wouldn't make sense for SQLite or Postgres,
Moreover, the table engine doesn't make any difference from the app's point
of view, so I think it's better to leave that to your database console.
Cheers,
Thomas
2012/9/16 Gurpreet Bhatia <gurpreetbhatia....@gmail.com>
> corrected the wrong subject :)
>
> On Sun, Sep 16, 2012 at 12:22 PM, Gurpreet Bhatia <
> gurpreetbhatia....@gmail.com> wrote:
>
>> Hi Everyone,
>>
>> I have one query:
>>
>> Should we change the database(mySQL) table's engine through migration
>> scripts or not? If not then why?
>>
>> Following were my proposal:
>>
>> def forwards(self, orm):
>>
>> # Change engine from MYISAM to INNODB
>> db.execute('alter table abc ENGINE=INNODB;')
>>
>> def backwards(self, orm):
>>
>> # Revert Engine to MYISAM
>> db.execute('alter table abc ENGINE=MYISAM;')
>>
>> - gurpreet
>>
>
>
>
> --
>
> Gurpreet Bhatia,
> If u feel like doin some work.......,
> sit down n......
> .....wait until that feeling goes away.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
