Forum: Ruby ANN: Sequel 4.2.0 Released

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
E106c35578b3e8bdca4f97ef3546f4f6?d=identicon&s=25 Jeremy E. (jeremyevans)
on 2013-09-02 20:18
Sequel is a lightweight database access toolkit for Ruby.

* Sequel provides thread safety, connection pooling and a concise
  DSL for constructing SQL queries and table schemas.
* Sequel includes a comprehensive ORM layer for mapping records to
  Ruby objects and handling associated records.
* Sequel supports advanced database features such as prepared
  statements, bound variables, stored procedures, savepoints,
  two-phase commit, transaction isolation, master/slave
  configurations, and database sharding.
* Sequel currently has adapters for ADO, Amalgalite, CUBRID,
  DataObjects, DB2, DBI, Firebird, IBM_DB, Informix, JDBC, MySQL,
  Mysql2, ODBC, OpenBase, Oracle, PostgreSQL, SQLite3, Swift, and

Sequel 4.2.0 has been released!

= New Features

* LATERAL subqueries are now supported on PostgreSQL 9.3+, HSQLDB,
  and DB2 via Dataset#lateral:

    DB.from(:a, DB[:b].where(:c=>:a__d).lateral)
    # SELECT * FROM a,
    # LATERAL (SELECT * FROM b WHERE (c = a.d)) AS t1

  You can use a similar syntax when joining tables:

    # SELECT * FROM a

  If you are using Microsoft SQL Server, you can use the new
  mssql_emulate_lateral_with_apply extension to emulate LATERAL
  subqueries via CROSS/OUTER APPLY.

* The static_cache plugin now supports a :frozen=>false option.  When
  this option is used, instead of returning the frozen cached values,
  the model now returns new, unfrozen objects that can be modified.
  Note that if you make any database modifications, you are
  responsible for updating the cache manually.

* A pg_static_cache_updater extension has been added.  This extension
  can automatically update the caches used by the static_cache plugin,
  whenever the underlying database table is updated, using PostgreSQL's
  notification channels.

  This works by defining triggers on the underlying model tables that
  use NOTIFY, and spinning up a thread in your application processes
  that uses LISTEN, and refreshes the cache for the related model
  whenever it receives a notification that the underlying table has
  been modified.

  This extension should make it possible to use the static_cache plugin
  with the :frozen=>false option for any table that is small and not
  frequently updated.

* A from_block extension has been added that makes Database#from operate
  like Dataset#from in regards to a passed block, allowing you to write
  code like:

    DB.from{table_returning_function(arg1, arg2)}

* Database#supports_partial_indexes? has been added for checking for
  partial index support.  Partial indexes are now supported on SQLite

* A pg_loose_count extension has been added for fast approximate counts
  of PostgreSQL tables.  This uses the system tables and should be
  fairly accurate if the table statistics are up to date:


* The Dataset#use_cursor method in the postgres adapter now supports
  a :cursor_name option.  You can set this option if you want to
  use nested cursors.

* The mysql2 adapter now supports a :flags Database option allowing to
  set custom mysql2 flags (e.g. ::Mysql2::Client::MULTI_STATEMENTS).

= Other Improvements

* Dataset#freeze has been implemented.  Previously, it was not
  implemented, so Object#freeze was used, which resulted in a dataset
  that wasn't cloneable.  Dataset#freeze now works as expected,
  resulting in a cloneable dataset, but it doesn't allow methods to
  be called that mutate the receiver.

* Dataset#dup has been implemented.  Previously, it was not
  implemented, so Object#dup was used, which resulted in a dataset
  that shared an options hash with the receiver, so modifying the
  dup's opts could also change the original dataset. Now dup works
  similarly to clone, except that the returned object will not be

* Model#dup has been implemented.  Previously, it was not implemented,
  so Object#dup was used, which resulted in a model instance that
  shared the values hash with the receiver, so modifying the dup's
  values also changed the original's values.  Now, dup does a shallow
  copy of some of the internal data structures as well, so the copy
  is more independent.

  Note that you still need to be careful if you mutate objects:

    m =>'a')
    m2 = m.dup
    m.a.gsub!('a', 'b') # also changes m2

* Model#clone has been implemented.  Previously, it had the same
  issues as dup.  Now, it calls the new Model#dup, but also
  freezes the returned object if the receiver is frozen.

* Placeholder literal strings with an empty parameter hash are now
  handled correctly.

= Backwards Compatibility

* The static_cache plugin now disallows saving/destroying instances
  unless the :frozen=>false option is used.  As the cached objects
  returned by the model were frozen anyway, this affects creating
  new instances or saving/destroying instances returned from the
  underlying dataset.

* Model#set_values has been removed (it was deprecated starting in
  Sequel 4.0).

* The following Model class methods are no longer defined:
  insert_multiple, set, to_csv, paginate, query, set_overrides,
  set_defaults.  By default, these methods used call the
  dataset method of the same name, but as those methods are no
  longer defined on datasets by default, they also resulted in a

* Dataset#query!, #set_defaults!, and #set_overrides! are no longer
  defined on all datasets.  They are now only defined on datasets
  that use the query or set_overrides extensions.

* Partial indexes are no longer returned by Database#indexes on MSSQL,
  for consistency with PostgreSQL.  Note that the same change was
  desired for SQLite, but SQLite currently does not offer reflection
  support for determining which indexes are partial.

* Database#foreign_key_list on MSSQL now will return a
  SQL::QualifiedIdentifier instead of a symbol for the :table entry if
  the schema of the referenced table does not match the schema of the
  referencing table.


* {Website}[]
* {Source code}[]
* {Blog}[]
* {Bug tracking}[]
* {Google group}[]
* {RDoc}[]
This topic is locked and can not be replied to.