On Thu, Jan 8, 2009 at 9:07 AM, Martin Hawkins <martin.hawk...@gmail.com> wrote:
> The database is a legacy SQL Server db with over 100 tables already in > existence. > 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 > table. > 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, just 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 Schroeder ------------------------ hassan.schroe...@gmail.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
