On Apr 19, 3:45 am, Roland Swingler <[email protected]> wrote: > Some more MySql specific features would be good (although I'm aware > that there is a slight antipathy towards MySql here). Being able to > write SQL in ruby rather than "String-programming" seems to be a big > benefit of Sequel, so it would be great to be able to do this as much > as possible. Specific things I find myself needing are: "load data > infile", which should be relatively easy to implement, and index > hinting - working with any reasonably sized dataset in MySQL seems to > pretty much require USE INDEX in order to get any sort of decent > performance.
I'm happy to apply adapter specific patches assuming they come with specs. > I'm happy to work on these myself when I get time - although I'm not > initially sure how the index hinting would fit in. Maybe as another > method on symbol if you're using the MySQL adapter - something > like :my_table.use_index(:index_name, :for => :join) ? Unfortunately, I don't think that any core extensions should be added for adapter specific behavior. You'll have to write a custom extension for that. > Also, I'm curious as to whether it would be easy or hard to replace > the usage of the underlying mysql driver with something like > neverblockhttp://www.espace.com.eg/neverblock/blog/2008/08/28/neverblock-mysql-... > or mysqlplushttp://github.com/oldmoe/mysqlplus- it would be good if > it wasn't just ActiveRecord that got all the Async attention. A good > presentation on all this is > here:http://www.igvita.com/2010/04/15/non-blocking-activerecord-rails/ Sequel already uses mysqlplus if it is available, falling by to the standard mysql driver if it is not. 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.
