sequel 4.26.0 → 5.37.0

data/doc/release_notes/4.12.0.txt

@@ -1,105 +0,0 @@
-= New Features
-
-* Database#schema now includes :max_length entries for string
-  columns, specifying the size of the string field.  The
-  auto_validations plugin now uses this information to
-  automatically set up max_length validations on those fields.
-
-* The Dataset join methods now support a :reset_implicit_qualifier
-  option.  If set to false, this makes the join not reset the
-  implicit qualifier, so that the next join will not consider this
-  table as the last table joined.  Example:
-
-    DB[:a].join(:b, :c=>:d).
-      join(:e, :f=>:g)
-    # SELECT * FROM a
-    # INNER JOIN b ON (b.c = a.d)
-    # INNER JOIN e ON (e.f = b.g)
-
-    DB[:a].join(:b, {:c=>:d}, :reset_implicit_qualifier=>false).
-      join(:e, :f=>:g)
-    # SELECT * FROM a
-    # INNER JOIN b ON (b.c = a.d)
-    # INNER JOIN e ON (e.f = a.g)
-
-* The Dataset cross and natural join methods now accept an options
-  hash. Example:
-
-    DB[:a].cross_join(:b, :table_alias=>:c)
-    # SELECT * FROM a CROSS JOIN b AS c
-
-* Model#set_nested_attributes has been added to the nested_attributes
-  plugin, which allows you to to set the nested_attributes options to
-  use per-call.  This is very helpful if you have multiple forms that
-  handle associated objects, but with different input fields used
-  for the associated objects depending on the form.  Example:
-
-    album.set_nested_attributes(:tracks,
-      params[:track_attributes],
-      :fields=>[:a, :b, :c])
-
-* Database#values has been added on PostgreSQL, which creates a
-  dataset that uses VALUES instead of SELECT.  Just as PostgreSQL
-  allows, you can also use orders, limits, and offsets with this
-  dataset.
-
-* A :notice_receiver option is now supported in the postgres adapter
-  if the pg driver is used.  This should be a proc, which will be
-  passed to the pg connection's set_notice_receiver method.
-
-* A Database :readonly option is now supported in the sqlite adapter,
-  which opens the database in a read-only mode, causing an error
-  if a query is issued that would modify the database.
-
-* A :before_thread_exit option has been added to
-  Database#listen_for_static_cache_updates in the
-  pg_static_cache_updater extension, allowing you to run code before
-  the created thread exits.
-
-= Other Improvements
-
-* Eager loading limited associations using a UNION now works
-  correctly when an association block is used.  This fixes a
-  regression that first occurred in 4.10.0, when the union
-  eager loader became the default eager loader.
-
-* When creating a new associated object in the nested_attributes
-  plugin, where the reciprocal association is a many_to_one
-  association, set the cached reciprocal object in the new
-  associated object before saving it.
-
-  This fixes issues when validations in the associated object
-  require access to the current object, which may not yet be
-  saved in the database.
-
-* The prepared_statements and prepared_statements_associations
-  plugins now automatically use explicit column references when
-  preparing statements.  This fixes issues on PostgreSQL when a
-  column is added to a table while a prepared statement exists
-  that selects * from the table.  Previously, all further attempts
-  to use the prepared statement will fail.
-
-  This allows you to run migrations that add columns to tables
-  while concurrently running an application that uses the
-  prepared statements plugins.  Note that many other schema
-  modifications can cause issues when running migrations
-  while concurrently running an application, but most of those
-  are not specific to usage of prepared statements.
-
-* Dataset#insert_select on PostgreSQL now respects an existing
-  RETURNING clause, and won't override it to use RETURNING *.
-
-  A similar fix was applied to the generalized prepared statements
-  support as well.
-
-* The interval parser in the pg_interval extension now supports
-  intervals with 2-10 digits for hours.  Previously, it only
-  supported using 2 digits for hours.
-
-= Backwards Compatibility
-
-* The methods and classes deprecated in 4.11.0 have been removed.
-
-* The nested_attributes internal API has changed significantly. If
-  you were calling any private nested_attributes methods, you'll
-  probably need to update your code.

data/doc/release_notes/4.13.0.txt

@@ -1,169 +0,0 @@
-= New Features
-
-* A modification_detection plugin has been added, for automatic
-  detection of in-place column value modifications.  This makes
-  it so you don't have to call Model#modified! manually when
-  changing a value in place.
-
-* A column_select plugin has been added, for automatically
-  selecting explicitly qualified columns in model datasets.
-  Example:
-
-    Sequel::Model.plugin :column_select
-    class Album < Sequel::Model
-    end
-    Album.dataset.sql
-    # SELECT albums.id, albums.name, albums.artist_id
-    # FROM albums
-
-* An insert_returning_select plugin has been added, for automatically
-  setting up RETURNING clauses for models that select explicit
-  columns.  This is useful when using the column_select or
-  lazy_attributes plugins.
-
-* A pg_enum extension has been added, for easier dealing with
-  PostgreSQL enum types.  The possible values for the type
-  are then returned in the schema hashes under the :enum_values
-  key.  It also adds create_enum, drop_enum, and add_enum_value
-  Database methods for migration support.
-
-* A round_timestamps extension has been added, for automatically
-  rounding timestamps to database supported precision when
-  literalizing.
-
-* A dataset_source_alias extension has been added, for automatically
-  aliasing datasets to their first source, instead of using t1, t2.
-  Example:
-
-    DB.from(:a, DB[:b]).sql
-    # SELECT * FROM a, (SELECT * FROM b) AS t1
-
-    DB.extension(:dataset_source_alias)
-    DB.from(:a, DB[:b]).sql
-    # SELECT * FROM a, (SELECT * FROM b) AS b
-
-* On Microsoft SQL Server, Sequel now emulates RETURNING support
-  using the OUTPUT clause, as long as only simple column references
-  are used.
-
-= Other Improvements
-
-* A regression has been fixed in the timestamps and table
-  inheritance plugins, where column values would not be
-  saved when skipping validations.  This was first broken in
-  4.11.0.
-
-* A regression has been fixed on JRuby and Rubinius when using
-  Sequel::Model(dataset) if the dataset needs to literalize a
-  symbol (and most do).  This was first broken in 4.10.0.
-
-* Primary keys are now automatically setup for models even if
-  the models select specific columns.
-
-* The lazy_attributes plugin now uses qualified columns in its
-  selection, instead of unqualified columns.
-
-* When looking up model instances by primary key, Sequel now uses a
-  qualified primary key if the model uses a joined dataset.
-
-* For associations that require joins, Sequel will now use the
-  associated model's selection directly (instead of
-  associated_table.*) if the associated model's selection consists
-  solely of qualified columns.
-
-  Among other things, this means that a many_to_many association to 
-  a model that uses lazy attributes will not eagerly load the lazy
-  attributes by default.
-
-* Model#save now uses insert_select if there is an existing
-  RETURNING clause used by the underlying dataset, even if the model
-  selects specific columns.
-
-* In Dataset#insert, aliased tables are now automatically unaliased.
-  This allows you to use a dataset with an aliased table and have
-  full SELECT/INSERT/UPDATE/DELETE support, assuming the database
-  supports aliased tables in UPDATE and DELETE.
-
-* Dataset#graph now qualifies columns correctly if the current
-  dataset is a joined dataset and it moves the current dataset to
-  a subselect.
-
-* Dataset#joined_dataset? is now a public method, and can be used to
-  determine whether the dataset uses a join, either explicitly via
-  JOIN or implicitly via multiple FROM tables.
-
-* The Dataset#unqualified_column_for helper method has been added,
-  returning the unqualified version of a possibly qualified column.
-
-* The composition and serialization plugins now support validations
-  on the underlying columns.  Previously, they didn't update the
-  underlying columns until after validations were performed.  This
-  works better when using the auto_validations plugin.
-
-* The class_table_inheritance plugin now uses JOIN ON instead of
-  JOIN USING, which makes it work on all databases that Sequel
-  supports.  Additionally, the plugin now explicitly selects
-  qualified columns from all of the tables.
-
-* The list plugin now adds an after_destroy hook that will renumber
-  rows after the current row, similar to how moving existing values
-  in the list works.
-
-* The pg_json extension is now faster when json column value is a
-  plain string, number, true, false, or nil, if the underlying json
-  library handles such values natively.
-
-* External jdbc, odbc, and do subadapters can now be loaded
-  automatically without requiring them first, assuming proper
-  support in the external subadapter.
-
-* When using create_table on MySQL, correctly handle the :key
-  option to when calling foreign_key with a column reference.
-
-* On Oracle, use all_tab_cols instead of user_tab_cols for getting
-  default values when parsing the schema.  This makes it work if the
-  user does not own the table.
-
-* On Oracle, use all_tables and all_views for Database#tables and
-  Database#views.  This works better for users with limited rights.
-
-* Additional disconnect errors are now recognized in the postgres and
-  jdbc/mysql adapters.
-
-* Sequel::Model now uses copy constructors (e.g. initialize_copy)
-  instead of overriding #dup and #clone.
-
-* The rake default task now runs plugin specs in addition to
-  core and model specs.
-
-= bin/sequel Improvements
-
-* Add the sequel lib directory to the front of the load path
-  instead of the end, fixing cases where you end up requiring an
-  old version of the sequel gem (e.g. by using sequel_pg).
-
-* Add the sequel lib directory as an absolute path, fixing cases
-  where you later change the current directory.
-
-* Require sequel later in the code, so that bin/sequel -h doesn't
-  need to require sequel, and full backtrace is not printed if
-  requiring sequel raises an error (unless -t is used).
-
-* If an exception is raised, put a newline between the exception
-  message and backtrace.
-
-* Don't allow usage of -C with any of -cdDmS.
-
-* If sequel -v is given along with a database or code string to
-  execute, print the Sequel version but also continue, similar
-  to how ruby -v works.
-
-= Backwards Compatibility
-
-* The switch from JOIN ON to JOIN USING in the
-  class_table_inheritance can break certain usage, such as querying
-  using unqualified primary key.  Users should switch to using a
-  qualified primary key instead.
-
-* Calling Dataset#returning when the underlying database does not
-  support it now raises an Error.

data/doc/release_notes/4.14.0.txt

@@ -1,68 +0,0 @@
-= New Features
-
-* Delayed evaluation blocks can now accept the dataset literalizing
-  the delayed evaluation as an argument.  This makes it so the
-  delayed evaluation result can depend on the dataset doing the
-  literalization:
-
-    ds = DB[:a].where(Sequel.delay do |ds|
-      {Sequel.qualify(ds.first_source, :col)=>1}
-    end)
-    ds.sql          # SELECT * FROM a WHERE (a.col = 1)
-    ds.from(:b).sql # SELECT * FROM b WHERE (b.col = 1)
-
-* Database#create_trigger on PostgreSQL now supports a :when option
-  to create a filter for the trigger, so that it is only triggered
-  when the filter condition is true.
-
-* You can now override the cache key prefix in the caching plugin
-  by overriding the cache_key_prefix class method.  This can be
-  useful when using a table inheritance plugin.
-
-= Other Improvements
-
-* You can now pass arbitrary types to Dataset#where and related
-  methods.  Previously, if a type was not explicitly handled, an
-  exception would be raised.  Now you can pass any object that can
-  be literalized.  The only exception is that you can't pass
-  Numeric objects, since #where and similar methods should
-  only deal with boolean expressions.
-
-* association_join and related methods now work correctly if the
-  dataset already has an explicit selection.
-
-* A regression has been fixed in the class_table_inheritance plugin
-  when using a hierarchy of more than 2 levels, when using the
-  superclass to load a subclass instance more than 2 levels below,
-  and later attempting to load a column contained in one of the
-  middle tables.
- 
-* When using _delete or _remove keys in the nested_attributes plugin
-  to remove existing associated objects, the associated objects are
-  now deleted from the cached association array at time of call.
-  This is for consistency when adding new associated objects, where
-  the new associated objects are added to the cached association
-  array at time of call.
-
-* The nested_attributes plugin now handles composite primary keys
-  correctly when working around validation issues for one_to_one
-  and one_to_many associations.
-
-* If exception A is raised during a transaction, and exception B
-  is raised while attempting to rollback the transaction, the
-  transaction code will now raise exception A instead of exception B.
-
-* An additional serialization failure is now detected on PostgreSQL.
-
-* An additional disconnect error is now recognized in the jdbc/jtds
-  adapter.
-
-* The code examples in the RDoc are now syntax highlighted, and
-  many minor fixes to the code examples in the RDoc were made.
-  Additionally, many other improvements were made to the RDoc.
-
-= Backwards Compatibility
-
-* Dataset#delayed_evaluation_sql_append now accepts the delayed
-  evaluation as an argument, instead of the callable contained by the
-  delayed evaluation.

data/doc/release_notes/4.15.0.txt

@@ -1,56 +0,0 @@
-= New Features
-
-* fdbsql and jdbc/fdbsql adapters have been added, for connecting to
-  FoundationDB SQL Layer.
-
-* A split_values plugin has been added, for moving non-column entries
-  from the values hash into a separate hash.  This allows you to
-  select additional columns (e.g. computed columns) when retrieving
-  model instances, and be able to save those instances without
-  removing the additional columns.
-
-* A Sequel::Model.cache_associations accessor has been added, which
-  can be set to false to not cache any association metadata.  This
-  can fix issues in a development environment that uses code
-  reloading.
-
-* The active_model plugin now supports activemodel 4.2.0beta1.
-
-* More PostgreSQL array types are handled automatically by the
-  pg_array extension, such as xml[] and uuid[].
-
-* Creating foreign tables is now supported on PostgreSQL via the
-  :foreign and :options create_table options.
-
-* The :nolog Database option is now supported in the informix
-  adapter, where it disables the use of transactions.
-
-* PlaceholderLiteralizer#with_dataset has been added, allowing you
-  to create another PlaceholderLiteralizer with a modified dataset,
-  useful if you want to change the row_proc or any non-SQL dataset
-  options.
-
-= Other Improvements
-
-* The tactical_eager_loading plugin once again works correctly with
-  limited associations.
-
-* A bug in older versions of MySQL is now worked around when schema
-  dumping a table with multiple timestamp columns.
-
-* On PostgreSQL, create_view(:view_name, dataset, :materialized=>true)
-  is now reversible.
-
-* Postgres::{JSON,JSONB}Op#to_record and #to_recordset no longer take
-  an optional argument.  This was supported in PostgreSQL 9.4beta1,
-  but removed before PostgreSQL 9.4beta2.
-
-* Dataset#insert now returns the last inserted id in the informix
-  adapter.
-
-* Sequel no longer raises an exception in
-  AssociationReflection#reciprocal if the associated class has an
-  association that does not have a valid associated class.
-
-* Sequel now raises an exception if a primary key is necessary to use
-  an association, but the model does not have a primary key.

data/doc/release_notes/4.16.0.txt

@@ -1,36 +0,0 @@
-= New Features
-
-* Model#qualified_pk_hash has been added, which is similar to
-  Model#pk_hash, but uses qualified keys.
-
-* Dataset#distinct now accepts a virtual row block.
-
-* Database#drop_table with :foreign=>true option now drops foreign
-  tables on PostgreSQL.  Database#create_table with :foreign option
-  is now reversible on PostgreSQL.
-
-= Other Improvements
-
-* Sequel::Model.cache_associations = false now skips the database's
-  schema cache when loading the schema for a model.  This fixes
-  some issues in environments that use code reloading.
-
-* Database#create_table? and #create_join_table? no longer use
-  IF NOT EXISTS if indexes are being created.
-
-* Model.primary_key_hash and .qualified_primary_key_hash have been
-  optimized.
-
-* validates_unique in the validation_helpers plugin now uses a
-  qualified primary key if the model's dataset is joined.  This fixes
-  a case when the auto_validations and class_table_inheritance
-  plugins are used together.
-
-* Disconnect errors are now recognized in the postgres adapter when
-  SSL is used for connecting.
-
-* Empty string default values are no longer converted to nil default
-  values on MySQL.
-
-* Database#foreign_key_list now works correctly on Microsoft SQL
-  Server 2005.

data/doc/release_notes/4.17.0.txt

@@ -1,38 +0,0 @@
-= New Features
-
-* A :preconnect Database option has been added, for automatically
-  creating the maximum number of connections to the database on
-  instantiation.  This is useful when there is high latency for
-  initial connection setup, where Sequel's usual approach of
-  connecting as needed can cause pauses at runtime.
-
-* Database#sharded? has been added for checking whether the Database
-  object uses multiple servers. 
-
-* Dataset#server? has been added, for returning a cloned dataset
-  associated with the given server/shard if the dataset does not
-  already have a server set.  This returns the receiver if the
-  server has already been set or the Database is not sharded.
-
-= Other Improvements
-
-* Sequel now uses the correct shard when deleting model instances.
-  Previously, the correct shard was only used in the unoptimized
-  case, not in the optimized case.
-
-* Sequel now uses the correct shard when using Dataset#insert_select
-  on PostgreSQL.  This was first broken in the 4.13.0 release.
-
-* Sequel now correctly handles Sequel::SQL::Blob instances used in
-  bound variables in the postgres adapter.  Previously this resulted
-  in duplicate apostrophes being used.
-
-* When using the jdbc/sqlite3 adapter with jdbc-sqlite3 3.8.7, Sequel
-  now handles date objects and empty blobs correctly, working around
-  bugs in the driver.
-
-= Backwards Compatibility
-
-* In the update_or_create plugin, Model.update_or_create now always
-  returns the object.  Previously it would not return the object if
-  the object already existed but no updates were necessary.