On Thu, Jan 8, 2009 at 9:07 AM, Martin H.
The database is a legacy SQL Server db with over 100 tables already in
I’ve noticed that db/schema.rb contains no information re the table
that was built, hence rake trying to re-create the schema_migrations
The first migration created a searches table:
And that was created with no errors? I assume you’ve looked in the
SQL Server error log(s)?
and the second migration tried to rename one of the columns:
So what does schema_migrations contain at this point?
Dropping the whole DB is really not an option.
Got it. But if I were you, I’d create a new temporary rails projects,
using sqlite3,. and try running your migrations there as a test. If they
work there, then there’s something peculiar to your original config.
Caveat: I know zero about MS SQL Server so…
Hassan S. ------------------------ email@example.com