On Mar 17, 3:20 pm, Scott LaBounty <[email protected]> wrote: > I guess what I was looking to do was start with no database (i.e. I removed > the test.db from my directory). I then wanted to run one of the two commands > to go to version one which is what I was trying to accomplish with what I > was showing below. Then I wanted check the database using the sqllite > Manager that I downloaded for Firefox and check that the database had the > table and the first column. Then finally, run a second command to pick up > the 002_ file and check the database again to make sure the second column > got added correctly. How does Sequel know which files in a directory to use. > In my case I had the two migration files, the data base, and the ruby file > for migrating all in the same directory. Is that allowed?
It is allowed and should work. I recommend removing the test.db file again and rerunning the migrations one at a time with the -E option to sequel. Then send an email with the contents of your migrations and the SQL generated so we can see what is going on. So, the commands you should run: rm test.db for x in *.rb; do echo $x; cat $x; done sequel -m . -M 1 -E sqlite://test.db sequel -m . -M 2 -E sqlite://test.db Send the output that those commands produce and hopefully it'll be easier to figure out what is going wrong. > Thanks again for the help and I'll see you at the LA Ruby conference, You're welcome. See you there. Thanks, Jeremy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en -~----------~----~----~----~------~----~------~--~---
