Got another one...  Dumper is creating:

    create_table(:hotelReviewSearchIndex) do
      Integer :hotelReviewId, :null=>false
      String :reviewSearchIndex, :text=>true, :null=>false

      index [:hotelReviewId], :name=>:hotelRevIdInd
      index [:reviewSearchIndex], :name=>:reviewSearch
    end

And on load to mysql, it errors out:

Mysql::Error BLOB/TEXT column 'reviewSearchIndex' used in key
specification without a key length


On May 22, 2:11 pm, Colin Steele <[email protected]> wrote:
> Definitely an improvement.  However, now the dumper code is dropping
> the default value for timestamp columns whose default is
> "CURRENT_TIMESTAMP".  Ie, used to generate:
>
> DateTime :dateModified, :default=>"CURRENT_TIMESTAMP".lit, :null=>false
>
> Now it's generating:
>
>       DateTime :dateModified, :null=>false
>
> An as an aside... the previously generated schema (with the default)
> choked mysql going back in on load/up.
>
> On May 21, 5:44 pm, Jeremy Evans <[email protected]> wrote:
>
> > On May 21, 10:41 am, Jeremy Evans <[email protected]> wrote:
>
> > > On May 21, 10:22 am, Vais Salikhov <[email protected]> wrote:
>
> > > > Oh, yes, feature in Sequel, and the bug is in how it's used in  
> > > > dump_schema_migration - lit shouldn't be used there.
>
> > > It's definitely a bug, and I was working on it yesterday.  I should be
> > > committing a patch today that fixes it.
>
> > I just pushed quite a few patches related to this area, the main one
> > beinghttp://github.com/jeremyevans/sequel/commit/ac87ba7d8122291fb277aa4d2...
>
> > Please give the master branch a test and let me know if it works for
> > you.
>
> > 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to