OK, I just tested and everything looks good. Scott
On Wed, Mar 18, 2009 at 10:28 AM, Scott LaBounty <[email protected]>wrote: > Jeremy, > > You're right, I'm using sequel 2.9.0. I'll upgrade and see how we do. > > Thanks again, > > Scott > > > On Wed, Mar 18, 2009 at 10:19 AM, Jeremy Evans <[email protected]>wrote: > >> >> On Mar 18, 7:39 am, Scott LaBounty <[email protected]> wrote: >> > I tried a few other things and the only thing I can get to work from >> > migration 001_ is the id: changing names, adding additional columns, >> etc. >> > will not happen. It seems like everything in 002_ will work including >> adding >> > more columns. >> > >> > I'm pretty confused right now. Is anyone actually using migrations? If >> so, >> > could you post a working example? I'm thinking I must be doing something >> > wrong but can't see it now. >> >> If I had to guess, you are using a version of Sequel prior to 2.10. >> Your results are what I would expect from an older version of Sequel, >> before support for database independent columns was added. I think >> this because your String :column_1 column isn't in the SQL, probably >> because it is calling Kernel#String and not >> Sequel::SQL::Generator#String (which wasn't added until 2.10). >> >> Jeremy >> >> >> > > > -- > Scott > http://steamcode.blogspot.com/ > -- Scott http://steamcode.blogspot.com/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
