Sequel: The Database Toolkit for Ruby
\nby Jeremy Evans<\/p>\n
He’s not the original implementer of the Sequel module. He’s improved it quite
\na bit. He added Jruby and Ruby 1.9 support, among other things.<\/p>\n
Sequel is a domian-spefic-language (DSL) for Ruby for dealing with databases.
\nIt’s not designed with web apps in mind, although it does work with them.<\/p>\n
He spoke very quickly, as he was constrained for time. Sounded interesting,
\nbut was a bit hard to follow due to the speed.<\/p>\n
sequel_model – an ORM build on Sequel<\/p>\n
He uses it successfully with the adaptors for Oracle, MySQL and PostgreSQL adaptors. Has a thread safe connection pool. Insures db connections aren’t leaked.<\/p>\n
Sequel::Dataset sets it apart from other Ruby db libraries.<\/p>\n
You can write complex SQL data queries without writing SQL, although you can if you want.<\/p>\n
– Dataset Graphing
\n– Pagination Support
\n– Create table, Schema modification, etc.
\n– Master\/Slave databases — requires no modifications to your code.
\n– Sharding\/Partitioning – simple to support with Sequel module
\n– Bound variables \/might\/ be faster, but don’t depend on it.
\n– Prepared statements are similar to bound variables, but potentially faster.
\nOnly use after profiling\/benchmarking.<\/p>\n
Has a command line client called ‘sequel’. The -E option causes all SQL to be
\nechoed to standard output.<\/p>\n
The future: Sequel 3.0. Many features will be moving to plugins, and the
\nmajority of the work is already complete. It’s going to be easier to use, and
\nrequire less memory.<\/p>\n
Q: Does it support sharded database migrations?<\/p>\n
A: No, not at this time. You can submit a patch.<\/p>\n","protected":false},"excerpt":{"rendered":"
Sequel: The Database Toolkit for Ruby by Jeremy Evans He’s not the original implementer of the Sequel module. He’s improved it quite a bit. He added Jruby and Ruby 1.9 support, among other things. Sequel is a domian-spefic-language (DSL) for Ruby for dealing with databases. It’s not designed with web apps in mind, although it … <\/p>\n