Forum: Ruby ANN: Sequel 4.4.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.
F183bcc4176b308c9edabe79299e448f?d=identicon&s=25 Jeremy Evans (jeremyevans)
on 2013-11-01 16:16
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, SQLAnywhere, SQLite3,
  Swift, and TinyTDS.

Sequel 4.4.0 has been released!

= New Features

* Sequel now supports Sybase SQLAnywhere, via the sqlanywhere and
  jdbc/sqlanywhere adapters.

* The filter by associations support now handles cases where the
  association has :conditions or a block (as long as the block
  does not rely on instance-specific behavior).  This allows
  you to handle the following:

    Album.many_to_many :popular_tags, :class=>:Tag do |ds|
      ds.where{tags__popularity > 9000}
    Album.where(:popular_tags=>[Tag[1], Tag[2]])

  This will return all albums whose popular_tags would include
  at least one of those two tags.  Previously, the block would
  be ignored, returning albums containing one those tags even if
  the tags weren't popular.

* A table_select plugin has been added that changes the default
  selection for models from * to table.*.  This is useful for
  people who want ActiveRecord-like behavior instead of SQL-like
  behavior, where joining tables doesn't automatically include
  columns in the other table.

  This can fix issues where joining another table that has columns
  with the same name as columns in the model table without
  specifying an explicit selection results in model objects being
  returned where the values in the model object are the values
  from the joined table instead of the model table.

* Dataset#offset has been added, for specifying offset separately
  from limit.  Previous this was possible via:

    ds.limit(nil, offset)

  but this is a friendlier API.

* The jdbc adapter now has support for foreign key parsing.  This
  is used if there is no specific support for the underlying

* Foreign key parsing is now supported on Oracle.

= Other Improvements

* Association add_*/remove_*/remove_all_* methods for
  pg_array_to_many associations now work on unsaved model objects.

* In the constraint_validations extension, deletes from the
  metadata table are now processed before inserts, so that dropping
  an existing constraint and readding a constraint with the same
  name now works correctly.

* Cloning an association now copies the :eager_block option
  correctly from the source association if it was passed as
  the block to the source association method.

* Cloning a cloned association now copies the block for the

* The descendants method in the tree plugin no longer modifies an
  array it is iterating over.

* The jdbc/postgresql adapter now supports PostgreSQL-specific types,
  with pretty much the same support as the postgres adapter.  When
  using the pg_* extensions, the dataset will now handle the
  PostgreSQL types correctly and return instances of the correct
  Ruby classes (e.g. hstore is returned as Sequel::Postgres::HStore).

  You should no longer need to use the typecast_on_load or
  pg_typecast_on_load plugins when using model objects that use these
  types when using the jdbc/postgresql adapter.

* Offset emulation on Oracle now handles cases where selected
  columns can't be ordered.

* Offset emulation on DB2 no longer automatically orders on all
  columns if the dataset itself is unordered.

* Types containing spaces are now returning correctly when
  parsing the schema in the oracle adapter.

* Database#tables no longer returns tables in the recycle bin on

* add_foreign_key now works correctly on HSQLDB, by splitting the
  column addition and constraint addition into two separate

* add_primary_key now works correctly on H2.


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