sequel 5.20.0 → 5.49.0

data/doc/release_notes/4.38.0.txt

@@ -1,67 +0,0 @@
-= New Features
-
-* Sequel::SQL::NumericMethods#coerce has been added, which adds
-  support for ruby's coercion protocol when performing numeric
-  operations.  Previously, Sequel supported code like:
-
-    Sequel.expr{a - 1}
-
-  This is because a in this case returns a Sequel::SQL::Indentifier,
-  which defines #- to return a Sequel::SQL::NumericExpression.  By
-  supporting #coerce, the following code now also works:
-
-    Sequel.expr{1 - a}
-
-  This is because Integer#- calls #coerce on the argument if it is
-  defined (ruby's coercion protocol).  Previously, you had to handle
-  this differently, using something like:
-
-    Sequel.expr(1) - a
-    # or
-    Sequel.-(1, a)
-
-* Sequel now supports the ** operator for exponentiation on
-  expressions, similar to the +, -, *, and / operators.  Sequel uses
-  the database power function to implement this by default on the
-  databases that support it (most of them).  On Access, it uses the ^
-  operator, on Derby it is emulated using a combination of exp/ln
-  (with some loss of precision).  SQLite doesn't support a power
-  function at all, but Sequel emulates it using multiplication for
-  known integer exponents.
-
-* Sequel::SQLTime.date= has been added, which allows you to set the
-  date used for Sequel::SQLTime instances.  Sequel::SQLTime is a
-  subclass of Time that is literalized using only the time components,
-  and is the ruby class used to store values of database time columns
-  on most adapters.  Sequel::SQLTime defaults to using the current
-  date, but you can now set a specific date, for more consistency with
-  some drivers (Mysql2 uses 2000-01-01, tiny_tds uses 1900-01-01).
-
-* The postgres adapter now supports a :driver_options option when
-  using the pg driver, which is passed directly to pg.  This can be
-  used to specify a client SSL certificate or to specify the
-  certificate authority root certificate when using
-  :sslmode=>'verify-full'.
-
-= Other Improvements
-
-* Sequel no longer uses after_commit/rollback database hooks by
-  default if the after_commit/after_rollback model methods are not
-  overridden. This provides a performance speedup, but the main
-  benefit is that it no longer causes memory issues when saving a
-  large number of model instances in a single transaction, and it
-  also works with prepared transactions/2 phase commit.  You can
-  still set use_after_commit_rollback= manually to force the
-  after_commit/rollback setting.
-
-  Note that Sequel 5 will move after_commit/rollback model hooks to
-  a plugin, and the default and recommended approach will be to use
-  the database after_commit/rollback hooks in the after_save or
-  similar model hooks.
-
-= Backwards Compatibility
-
-* The Sequel::Model use_after_commit_rollback class and instance
-  methods now return nil by default instead of true.  nil now
-  indicates the default behavior of checking whether the appropriate
-  model hook has been defined, and only adding a database hook if so.

data/doc/release_notes/4.39.0.txt

@@ -1,127 +0,0 @@
-= New Features
-
-* Sequel.[] has been added as an alias to Sequel.expr. This makes it
-  a little easier to get Sequel-specific objects:
-
-    Sequel[:table].*                  # "table".*
-    Sequel[:table__column].as(:alias) # "table"."column" AS "alias"
-    Sequel[:column] + 1               # ("column" + 1)
-
-* The timestamps plugin now supports an :allow_manual_update option.
-  If this option is used, the timestamps plugin will not override the 
-  update timestamp when saving if the user has modified it since
-  retrieving the object.
-
-* The touch plugin now also touches associations on create in addition
-  to update and delete.
-
-* The IntegerMigrator now supports a :relative option, which will
-  migrate that many migrations up (for positive numbers) or down (for
-  negative numbers).
-
-* Database#rollback_checker has been added, which returns a callable
-  that can be called later to determine whether the transaction ended
-  up committing or rolling back.  So if you may need to check
-  transaction status at some future point, and don't need immediate
-  action on rollback/commit, it is better to use a rollback checker
-  than to add an after commit/rollback hook.
-
-    rbc = nil
-    DB.transaction do
-      rbc = DB.rollback_checker
-      rbc.call #=> nil
-    end
-    rbc.call # => false
-
-    DB.transaction(:rollback=>:always) do
-      rbc = DB.rollback_checker
-    end
-    rbc.call # => true
-
-* The add_column schema method now supports an :if_not_exists option
-  on PostgreSQL 9.6+, which will only add the column if it does not
-  already exist:
-
-    DB.add_column :t, :c, Integer, :if_not_exists=>true
-    # ALTER TABLE "t" ADD COLUMN IF NOT EXISTS "c" integer
-
-* The add_column schema method now supports an :after and :first
-  option on MySQL to add the column after an existing column or as
-  the first column:
-
-    DB.add_column :t, :c, Integer, :first=>true
-    # ALTER TABLE `t` ADD COLUMN `c` integer FIRST
-    DB.add_column :t, :c1, Integer, :after=>:c2
-    # ALTER TABLE `t` ADD COLUMN `c1` integer AFTER `c2`
-
-* JSONBOp#insert has been added to the pg_json_ops extension, which
-  supports the new jsonb_insert function added in PostgreSQL 9.6+:
-
-    Sequel.pg_jsonb_op(:c).insert(%w'0 a', 'a'=>1)
-    # jsonb_insert("c", ARRAY['0','a'], '{"a":1}'::jsonb, false)
-
-* Dataset#full_text_search on PostgreSQL now supports a
-  :to_tsquery=>:phrase option, to enable the native phrase searching
-  added in PostgreSQL 9.6+:
-
-    DB[:t].full_text_search(:c, 'foo bar', :to_tsquery=>:phrase)
-    # SELECT * FROM "t"
-    # WHERE
-    #   (to_tsvector(CAST('simple' AS regconfig), (COALESCE("c", '')))
-    #   @@ phraseto_tsquery(CAST('simple' AS regconfig), 'foo bar'))
-
-* Sequel::Database.set_shared_adapter_scheme has been added, allowing
-  external adapters to add support for Sequel's mock adapter.
-  External adapters should have a shared adapter requirable at
-  sequel/adapters/shared/adapter_name, that uses the following
-  format:
-
-    # in sequel/adapters/shared/mydb
-    module Sequel::MyDB
-      Sequel::Database.set_shared_adapter_scheme :mydb, self
-
-      def self.mock_adapter_setup(db)
-        # Any mock-adapter specific setup to perform on the
-        # given Database instance
-      end
-
-      module DatabaseMethods
-        # methods for all Database objects using this adapter
-      end
-
-      module DatasetMethods
-        # methods for all Dataset objects using this adapter
-      end
-    end
-
-
-= Other Improvements
-
-* The hook_class_methods plugin only adds a Database transaction
-  hook if one of the after commit/rollback hook class methods is
-  actually used.  This means that loading the plugin no longer
-  keeps all saved/deleted objects in memory until transaction
-  commit.
-
-* The active_model plugin now uses a rollback checker instead of
-  an after_rollback hook, so models that use the active_model plugin
-  no longer store all saved model instances in memory until
-  transaction commit.
-
-* When using the IntegerMigrator, attempting to migrate to a
-  migration number above the maximum will now migrate to the lastest
-  version, and attempting to migrate to a migration number below 0
-  will now migrate all the way down.
-
-* The pg_interval extension now supports ActiveSupport::Duration
-  objects that use week and hour parts (new in ActiveSupport 5).
-
-= Backwards Compatibility
-
-* The change to the touch plugin to touch associations on create could
-  possibly affect existing behavior, so if you are using this plugin,
-  you should test that this does not cause any problems.
-
-* External adapters that tried to add support for the mock adapter
-  now need to update their code to use the new
-  Sequel::Database.set_shared_adapter_scheme method.

data/doc/release_notes/4.4.0.txt

@@ -1,92 +0,0 @@
-= 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}
-    end
-    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
-  database.
-
-* 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
-  association.
-
-* 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
-  Oracle.
-
-* add_foreign_key now works correctly on HSQLDB, by splitting the
-  column addition and constraint addition into two separate
-  statements.
-
-* add_primary_key now works correctly on H2.

data/doc/release_notes/4.40.0.txt

@@ -1,179 +0,0 @@
-= New Features
-
-* A Sequel.split_symbols setting has been added.  This setting is
-  true by default, so there is no change to backwards compatibility
-  by default.  However, users can now do:
-
-    Sequel.split_symbols = false
-
-  to disable the splitting of symbols.  This will make Sequel no
-  longer treat symbols with double or triple underscores as qualified
-  or aliased identifiers, instead treating them as plain identifiers.
-  It will also make Sequel no longer treat virtual row methods with
-  double underscores as qualified identifiers.  Examples:
-
-    # Sequel.split_symbols = true
-    :column                    # "column"
-    :table__column             # "table"."column"
-    :column___alias            # "column" AS "alias"
-    :table__column___alias     # "table"."column" AS "alias"
-    Sequel.expr{table__column} # "table"."column"
-
-    # Sequel.split_symbols = false
-    :column                    # "column"
-    :table__column             # "table__column"
-    :column___alias            # "column___alias"
-    :table__column___alias     # "table__column___alias"
-    Sequel.expr{table__column} # "table__column"
-
-  Disabling symbol splitting can make things much easier if leading
-  trailing, double, or triple underscores are used in identifiers
-  in your database.
-
-  Disabling symbol splitting makes Sequel simpler, even if it does
-  make it slightly less easy to create qualified and aliased
-  identifiers.  It is possible that the symbol splitting will be
-  disabled by default starting in Sequel 5.
-
-  Note that due to Database symbol literal caching, you should not
-  change the Sequel.split_symbols setting after creating a
-  Database instance.
-
-* SQL::Identifier#[] and SQL::QualifiedIdentifier#[] have been added
-  for creating qualified identifiers.  This makes it easier and more
-  natural to create qualified identifiers from existing identifiers.
-  Previously, you could do:
-
-    Sequel[:column].qualify(:table)
-
-  You can now use the more natural:
-
-    Sequel[:table][:column]
-
-  This can also be used in virtual rows:
-
-    Sequel.expr{table[:column]}
-
-  This offers a easy way to create qualified identifers when symbol
-  splitting has been disabled.
-
-* A symbol_aref extension has been added, allowing the use of
-  Symbol#[] to create qualified identifiers if passed a Symbol,
-  SQL::Identifier, or SQL::QualifiedIdentifier.  This doesn't
-  break any existing ruby behavior, as ruby currrently raises
-  an exception in such cases.  Example:
-  
-    :table[:column] # "table"."column"
-
-  This extension can make it easier to create qualified identifiers
-  if symbol splitting is disabled.
-
-  A symbol_aref_refinement extension has also been added, which
-  adds a refinement version of the extension that can be enabled via:
-
-    using Sequel::SymbolAref
-
-* A symbol_as extension has been added, which adds the Symbol#as method
-  to create aliased identifiers.  This was previously part of the core
-  extensions, but has been separated so it can be included by itself.
-  Example:
-
-    :column.as(:alias) # "column" AS "alias"
-
-  This extension can make it easier to create aliased identifiers if
-  symbol splitting is disabled.
-
-  A symbol_as_refinement extension has also been added, which
-  adds a refinement version of the extension that can be enabled via:
-
-    using Sequel::SymbolAs
-
-* An s extension has been added, which adds the Sequel::S module,
-  containing a private #S method that calls Sequel.expr.  You can
-  include this module in any module or class where you would like the
-  S method to be available:
-
-    class Album < Sequel::Model
-      extend Sequel::S
-      one_to_many :tracks, :order=>S(:number).desc
-    end
-
-  You can include this in Object if you want the S method to be
-  available globally:
-
-    Object.send(:include, Sequel::S)
-
-  Sequel::S also works if it is used as a refinement, adding the S
-  method to Object while the refinement is active:
-
-    using Sequel::S
-
-  This extension can make it easier to create qualified and aliased
-  identifiers if symbol splitting is disabled:
-
-    S(:table)[:column]
-    S(:column).as(:alias)
-
-* Dataset#insert_conflict on PostgreSQL now supports a :conflict_where
-  option, allowing for the handling of insert conflicts when using a
-  partial unique index:
-
-    DB[:table].insert_conflict(:target=>:a,
-      :conflict_where=>{:c=>true}).insert(:a=>1, :b=>2)
-    # INSERT INTO TABLE (a, b) VALUES (1, 2)
-    # ON CONFLICT (a) WHERE (c IS TRUE) DO NOTHING
-
-= Other Improvements
-
-* Sequel no longer attempts to combine arguments for non-associative
-  operators, as doing so leads to invalid code in cases such as:
-
-    Sequel.expr{column1 - (column2 - 1)}
-
-* Sequel now automatically adds NOT NULL constraints on columns when
-  adding a primary key constraint on the columns, if the database
-  doesn't handle that situation correctly.
-
-* Database#rollback_checker now returns a thread-safe object.
-
-* SQL::QualifiedIdentifier#initialize now converts SQL::Identifier
-  arguments to strings, fixing usage of such objects in the
-  schema methods.
-
-* The prepared_statements plugin now correctly handles lookup by
-  primary key on models with joined datasets.
-
-* The dataset_associations plugin now handles many_through_many and
-  one_through_many associations that use a single join table.  Note
-  there is no reason to create such associations, as many_to_many
-  and one_through_one associations will work for such cases.
-
-* The insert_returning_select plugin now handles cases where the
-  model doesn't have a valid dataset, fixing usage with the
-  lazy_attributes and dataset_associations plugins, and potentially
-  other plugins.
-
-* The column_select plugin no longer raises an exception if the
-  model's table does not exist.
-
-* The class_table_inheritance plugin now works when the
-  prepared_statements plugin is also used.
-
-* Some adapters now avoid thread-safety issues during loading on
-  ruby implementations without a GVL by avoiding the modification of
-  shared datastructures.
-
-* When using Database#tables with the :qualify=>true option on
-  PostgreSQL, table names with double or triple underscores are
-  now handled correctly.
-
-= Backwards Compatibility
-
-* The following Dataset constants are now frozen: NON_SQL_OPTIONS,
-  ACTION_METHODS, QUERY_METHODS, CONDITIONED_JOIN_TYPES,
-  UNCONDITIONED_JOIN_TYPES, and JOIN_METHODS.  Of these,
-  NON_SQL_OPTIONS was previously modified in a non-thread-safe manner
-  by some adapters.  External adapters should switch to having the
-  adapter's dataset non_sql_options method return an array of options
-  that do not affect the SELECT SQL for the adapter's datasets, rather
-  than modifying NON_SQL_OPTIONS.

data/doc/release_notes/4.41.0.txt

@@ -1,77 +0,0 @@
-= New Features
-
-* Dataset#with_* methods have been added as equivalents for a
-  few Dataset#*= methods, but instead of modifying the receiver, they
-  return a modified copy, similar to the dataset query methods.
-  Specific methods added:
-
-  with_extend :: Extends clone with given modules
-  with_row_proc :: Modifies row_proc in clone
-  with_quote_identifiers :: Modifies quote_identifiers setting in
-                            clone
-  with_identifier_input_method :: Modifies identifier_input_method
-                                  setting in clone
-  with_identifier_output_method :: Modifies identifier_output_method
-                                   setting in clone
-
-  Similarly, on Microsoft SQL Server, a with_mssql_unicode_strings
-  method has been added, which returns a clone with the
-  mssql_unicode_strings setting modified.
-
-* On DB2, Sequel now supports an :offset_strategy Database option,
-  which can be set to :limit_offset for "LIMIT X OFFSET Y" or
-  :offset_fetch for "OFFSET Y FETCH FIRST X ROWS ONLY".  Depending
-  on what version of DB2 is used and how DB2 is configured, it's
-  possible one of these strategies will work.  For backwards
-  compatibility, the current default is still to emulate offsets
-  using the ROW_NUMBER window function.
-
-* In the json_serializer plugin, you can now use an
-  Sequel::SQL::AliasedExpression instance as an association name
-  value, which allows you to rename the association in the resulting
-  JSON:
-
-    album.to_json(:include=>{Sequel.as(:album, :s)=>{:only=>:name}})
-    # => '{"id":1,"name":"RF","artist_id":2,"s":{"name":"YJM"}}'
-
-= Other Improvements
-
-* The association dataset methods now correctly handle cases where
-  one of the keys is nil.  Previously, they would incorrectly use an
-  IS NULL predicate in such cases.  Now, they use a false predicate.
-
-* The hook_class_methods plugin handling of commit hooks has been
-  fixed.  The implementation of commit hooks (but not rollback
-  hooks) was broken in hook_class_methods starting in 4.39.0 due to
-  changes to avoid keeping references to all model instances until
-  the transaction was committed or rolled back.
-
-* Using the Fixnum schema method no longer raises a warning on ruby
-  2.4+, as it now uses the Integer class instead of the Fixnum
-  constant.
-
-* The ado adapter has been greatly improved.  It now avoids memory
-  leaks, has much better type handling, and passes almost all specs.
-  Note that the ado adapter's behavior can change depending on the
-  version of ruby in use, try to use ruby 2.2+ for best compatibility.
-
-* Dataset#graph no longer mutates the receiver.  Previously, it set
-  an empty hash as the :graph option in the receiver, which was
-  unintentional and not desired.
-
-* Pure java exceptions that don't support the message= method are now
-  handled properly when reraising the exception on connection errors
-  in the jdbc adapter.
-
-= Backwards Compatibility
-
-* Support for using the Bignum constant as a generic type has been
-  removed, as was preannounced in the 4.36.0 release notes.  Users
-  should switch to using the :Bignum constant if they haven't already.
-
-* Users of the ado adapter may need to update their code now that the
-  ado adapter correctly handles most types.
-
-* The spec_*_w rake tasks in the repository now require ruby 2.4+ and
-  use the warning library for filtering warnings, instead of trying to
-  filter warnings with egrep.