Closed jazzdan closed 12 years ago
It appears that history_id is already set as the primary key on my MSSQL box, could that be the problem?
Yup, that could be why. Perhaps write a migration that does not use change but instead does an up/down.
That did the trick, thanks!
I ran across an error today migrating my SQL Server 2008 R2 database. The migration in question looks like this:
Here is my gemfile for good measure:
And here is the output when I try to run the migration:
Let me know if there is any other information I can provide that would be helpful. Thank you for all your hard work and effort!