Sha256: 4fda12106c8516fa25182b7389ed6c0bc0a274928c43d28fe50fb245dd25f6a1

Contents?: true

Size: 1.89 KB

Versions: 90

Compression:

Stored size: 1.89 KB

Contents

= New Features

* An insert_conflict plugin has been added for automatically handling
  constraint conflicts when saving new model instances.  It is
  supported on PostgreSQL 9.5+ and SQLite 3.24.0+.

    Album.new(name: 'Foo', copies_sold: 1000).
      insert_conflict(
        target: :name,
        update: {copies_sold: Sequel[:excluded][:b]}
      ).
      save

* On Microsoft SQL Server, the Database :ansi option has been added,
  which sets the following ANSI related options:

  * ANSI_NULLS
  * ANSI_PADDING
  * ANSI_WARNINGS
  * ANSI_NULL_DFLT_ON
  * QUOTED_IDENTIFIER
  * CONCAT_NULL_YIELDS_NULL

= Other Improvements

* Sequel.datetime_class = Time is now supported when using the
  named_timezones extension.  For backwards compatibility, the
  named_timezones extension still sets
  Sequel.datetime_class = DateTime.  When using Ruby 2.6+, the
  Time instances have the timezone set on them using Ruby 2.6+'s
  timezone support, but basic support works correctly in earlier
  versions of Ruby.

* On Microsoft SQL Server, Sequel now handles parsing schema for
  tables in another database on the same server or in a database
  on a linked server.

* The pg_json extension now correctly handles subclasses of core
  classes when wrapping objects.  This stopped working in Sequel
  5.21.0, when support for wrapping JSON primitives was added.

* Sequel now works around a couple bugs in jdbc-sqlite 3.27.2.1,
  allowing schema parsing and foreign key parsing to work.

* Dataset#execute* private methods now respect an explicitly given
  :server option, fixing Dataset#paged_each in the postgres adapter
  when using sharding.

* Timezone offsets are now handled correctly when typecasting an array
  or hash to datetime when Sequel.datetime_class = Time.

* Sequel now avoids errors when parsing schema when using the mock
  SQLite adapter.

* A minor thread-safety issue has been fixed in the named_timezones
  extension.

Version data entries

90 entries across 76 versions & 2 rubygems

Version Path
sequel-5.83.1 doc/release_notes/5.23.0.txt
sequel-5.83.0 doc/release_notes/5.23.0.txt
sequel-5.82.0 doc/release_notes/5.23.0.txt
sequel-5.81.0 doc/release_notes/5.23.0.txt
sequel-5.80.0 doc/release_notes/5.23.0.txt
sequel-5.79.0 doc/release_notes/5.23.0.txt
sequel-5.78.0 doc/release_notes/5.23.0.txt
sequel-5.77.0 doc/release_notes/5.23.0.txt
sequel-5.76.0 doc/release_notes/5.23.0.txt
sequel-5.75.0 doc/release_notes/5.23.0.txt
sequel-5.74.0 doc/release_notes/5.23.0.txt
sequel-5.73.0 doc/release_notes/5.23.0.txt
sequel-5.72.0 doc/release_notes/5.23.0.txt
sequel-5.71.0 doc/release_notes/5.23.0.txt
sequel-5.70.0 doc/release_notes/5.23.0.txt
sequel-5.69.0 doc/release_notes/5.23.0.txt
sequel-5.68.0 doc/release_notes/5.23.0.txt
sequel-5.67.0 doc/release_notes/5.23.0.txt
sequel-5.66.0 doc/release_notes/5.23.0.txt
sequel-5.65.0 doc/release_notes/5.23.0.txt