#827 ✓resolved
Greg Campbell

dm-migrations outputs incorrect CREATE TABLE SQL for MySQL

Reported by Greg Campbell | April 2nd, 2009 @ 06:39 PM | in 0.10.0

This one's my fault, so I'll submit a patch for it as well. dm-migrations currently outputs the table options (ENGINE, COLLATE, CHARACTER SET) before the columns, when they should show up after. This causes a MySQL error.

This also points out the need to have a true dm-migrations integration spec that actually runs migrations against a database for all supported adapters; we don't appear to have one at the moment, and it would have caught this problem immediately. I must have been running my ad-hoc integration test against an incorrect version of the gem.

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »


Referenced by