My list of features to add to Sequel is the lowest it has been since I took over maintaining it. Currently, there are two areas that I plan to work on:
Ruby 1.9 compatibility: Now that JRuby is officially supported, this is my next ruby platform target (Rubinius will be after Ruby 1.9). This will probably deal with send/send!, as well as Array.to_s, though there could be other bugs along the way. I don't expect 1.9 compatibility to take too long or to require many changes, but as I haven't used 1.9 at all, it may be much more involved. I think the biggest roadblock here is that my preferred OS (OpenBSD) doesn't have a ruby 1.9 package yet. Prepared Statements: This would allow you to prepare a statement once and call it multiple times with different inputs. This is potentially much faster on certain databases, up to 60% on PostgreSQL, and from what I've heard possibly more on Oracle. Here's how I think it should work: DB[:items].filter(:x=>:S?).prepare(:items_with_x) # Hopefully nobody uses a column named "S?" DB.call(:items_with_x, 2) # The equivalent of SELECT * FROM items WHERE x = 2, but faster The databases that don't support prepared statements but do support parametized queries could use the same interface. Also, if the database supports true stored procedures, it could use the same interface as well (you wouldn't need to use prepare on a dataset first). I welcome your thoughts in this area. 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 -~----------~----~----~----~------~----~------~--~---
