sequel 5.80.0 → 5.92.0

data/doc/release_notes/5.72.0.txt

@@ -1,33 +0,0 @@
-= New Features
-
-* A pg_auto_parameterize_in_array extension has been added, which
-  handles conversion of IN/NOT IN to = ANY or != ALL for more types.
-  The pg_auto_parameterize extension only handles integer types by
-  default, because other types require the pg_array extension. This
-  new extension adds handling for Float, BigDecimal, Date, Time,
-  DateTime, Sequel::SQLTime, and Sequel::SQL::Blob types.  It can
-  also handle String types if the :treat_string_list_as_text_array
-  Database option is present, using the text type for that. Handling
-  String values as text is not the default because that may cause
-  issues for some queries.
-
-= Other Improvements
-
-* The defaults_setter plugin now does a deep copy of database
-  default values that are hash/array or delegates to hash/array.
-  This fixes cases where the database default values are mutated.
-
-* Sequel now correctly handles infinite and NaN float values used
-  inside PostgreSQL array bound variables.
-
-* The data in the cache files used by the schema_caching and
-  index_caching extensions and static_cache_cache and
-  pg_auto_constraint_validations plugins are now sorted before the
-  cache file is saved, increasing consistency between runs.
-
-* bigdecimal has been added as a dependency.  bigdecimal is currently
-  a default gem in Ruby from 1.9 to 3.2, but it will move to a
-  bundled gem in Ruby 3.4, and there will be warnings in Ruby 3.3
-  for cases that will break in Ruby 3.4.  Adding bigdecimal as a
-  dependency should avoid warnings when using bundler in Ruby 3.3,
-  and should avoid errors in Ruby 3.4.

data/doc/release_notes/5.73.0.txt

@@ -1,66 +0,0 @@
-= New Features
-
-* A paged_operations plugin has been added, which adds support for
-  paged_datasets, paged_update, and paged_delete dataset methods.
-  This methods are designed to be used on large datasets, to split 
-  a large query into separate smaller queries, to avoid locking the
-  related database table for a long period of time.
-  paged_update and paged_delete operate the same as update and delete,
-  returning the number of rows updated or deleted. paged_datasets yields
-  one or more datasets representing subsets of the receiver, with the
-  union of all of those datasets comprising all records in the receiver:
-
-    Album.plugin :paged_operations
-
-    Album.where{name > 'M'}.paged_datasets{|ds| puts ds.sql}
-    # Runs: SELECT id FROM albums WHERE (name <= 'M') ORDER BY id LIMIT 1 OFFSET 1000
-    # Prints: SELECT * FROM albums WHERE ((name <= 'M') AND ("id" < 1002))
-    # Runs: SELECT id FROM albums WHERE ((name <= 'M') AND (id >= 1002)) ORDER BY id LIMIT 1 OFFSET 1000
-    # Prints: SELECT * FROM albums WHERE ((name <= 'M') AND ("id" < 2002) AND (id >= 1002))
-    # ...
-    # Runs: SELECT id FROM albums WHERE ((name <= 'M') AND (id >= 10002)) ORDER BY id LIMIT 1 OFFSET 1000
-    # Prints: SELECT * FROM albums WHERE ((name <= 'M') AND (id >= 10002))
-
-    Album.where{name <= 'M'}.paged_update(:updated_at=>Sequel::CURRENT_TIMESTAMP)
-    # SELECT id FROM albums WHERE (name <= 'M') ORDER BY id LIMIT 1 OFFSET 1000
-    # UPDATE albums SET updated_at = CURRENT_TIMESTAMP WHERE ((name <= 'M') AND ("id" < 1002))
-    # SELECT id FROM albums WHERE ((name <= 'M') AND (id >= 1002)) ORDER BY id LIMIT 1 OFFSET 1000
-    # UPDATE albums SET updated_at = CURRENT_TIMESTAMP WHERE ((name <= 'M') AND ("id" < 2002) AND (id >= 1002))
-    # ...
-    # SELECT id FROM albums WHERE ((name <= 'M') AND (id >= 10002)) ORDER BY id LIMIT 1 OFFSET 1000
-    # UPDATE albums SET updated_at = CURRENT_TIMESTAMP WHERE ((name <= 'M') AND (id >= 10002))
-
-    Album.where{name > 'M'}.paged_delete
-    # SELECT id FROM albums WHERE (name > 'M') ORDER BY id LIMIT 1 OFFSET 1000
-    # DELETE FROM albums WHERE ((name > 'M') AND (id < 1002))
-    # SELECT id FROM albums WHERE (name > 'M') ORDER BY id LIMIT 1 OFFSET 1000
-    # DELETE FROM albums WHERE ((name > 'M') AND (id < 2002))
-    # ...
-    # SELECT id FROM albums WHERE (name > 'M') ORDER BY id LIMIT 1 OFFSET 1000
-    # DELETE FROM albums WHERE (name > 'M')
-
-* A Dataset#transaction :skip_transaction option is now support to
-  checkout a connection from the pool without opening a transaction.  This
-  makes it easier to handle cases where a transaction may or not be used
-  based on configuration/options.  Dataset#import and Dataset#paged_each
-  now both support the :skip_transaction option to skip transactions.
-
-* Dataset#full_text_search now supports the to_tsquery: :websearch option
-  on PostgreSQL 11+, to use the websearch_to_tsquery database function.
-
-* The Sequel::MassAssignmentRestriction exception now supports model
-  and column methods to get provide additional information about the
-  exception.  Additionally, the exception message now includes information
-  about the model class.
-
-= Other Improvements
-
-* The ibmdb and jdbc/db2 adapter now both handle disconnect errors
-  correctly, removing the related connection from the pool.
-
-* Dataset#import no longer uses an explicit transaction if given a dataset
-  value, as in that case, only a single query is used.
-
-* The column_encryption plugin no longer uses the base64 library.  The
-  base64 library is moving from the standard library to a bundled gem
-  in Ruby 3.4, and this avoids having a dependency on it.

data/doc/release_notes/5.74.0.txt

@@ -1,45 +0,0 @@
-= New Features
-
-* Sequel.migration blocks now support a revert method, which reverts
-  the changes in the block on up, and applies them on down.  So if
-  you have a migration such as:
-
-    Sequel.migration do
-      change do
-        create_table :table do
-          # ...
-        end
-      end
-    end
-
-  and you later want to add a migration that drops the table, you
-  can use:
-
-    Sequel.migration do
-      revert do
-        create_table :table do
-          # ...
-        end
-      end
-    end
-
-  This will drop the table when migrating up, and create a table 
-  with the given schema when migrating down.
-
-* is_json and is_not_json methods have been added to the pg_json_ops
-  extension, for the IS [NOT] JSON operator supported in PostgreSQL
-  16+.  These were previously added in Sequel 5.59.0, and removed
-  in Sequel 5.61.0 as support was removed in PostgreSQL 15 beta 4.
-  PostgreSQL 16 shipped with support for them, so support has been
-  recommitted to Sequel.
-
-= Other Improvements
-
-* SQLite generated columns now show up in Database#schema when using
-  SQLite 3.37+.
-
-* Sequel now attempts to avoid an infinite loop in pathlogical cases
-  in the jdbc adapter, where the exception cause chain has a loop.
-  Additionally, if an exception is already recognized as a disconnect,
-  or an exception already responds to a getSQLState method, Sequel no
-  longer looks at the causes of the exception.

data/doc/release_notes/5.75.0.txt

@@ -1,35 +0,0 @@
-= New Features
-
-* Database#{defer,immediate}_constraints methods have been added on
-  PostgreSQL for changing handling of deferrable constraints inside
-  a transaction. defer_constraints sets deferrable constraints to
-  be deferred (not checked until transaction commit), and
-  immediate_constraints sets deferrable constraints to be checked
-  as part of the related query, and any already deferred constraint
-  checks to be applied immediately. You can pass the :constraints
-  option to only apply the changes to specific constraints.
-
-* TimestampMigrator.run_single has been added, to migrate a single
-  migration up or down.
-
-= Other Improvements
-
-* INSERT RETURNING is now supported on MariaDB 10.5+, and used
-  automatically when saving new model objects. Note that this
-  is not supported when using the jdbc adapter, because the
-  jdbc-mysql driver doesn't support it.  A jdbc/mariadb adapter
-  could be added, as it's likely recent versions of the
-  jdbc-mariadb driver would support it, but the jdbc-mariadb gem 
-  hasn't been updated in over 4 years.  Talk to the jdbc-mariadb
-  gem maintainers if you want to use this feature with the jdbc
-  adapter.
-
-* The Dataset#paged_each optimization in the postgres adapter
-  now respects the :skip_transaction option, making it the
-  same as the :hold option.  Note that this has effects beyond
-  just skipping the transaction, but non-HOLD cursors are only
-  supported inside transactions.
-
-* The any_not_empty? extension's Dataset#any? method now supports
-  an argument, passing it to Enumerable#any? (which has supported
-  an argument since Ruby 2.5).

data/doc/release_notes/5.76.0.txt

@@ -1,86 +0,0 @@
-= New Features
-
-* An auto_cast_date_and_time extension has been added, which will
-  automatically cast date and time values using SQL standard functions.
-  This makes sure the database will treat the value as a date, time,
-  or timestamp, instead of treating it as a string or unknown type:
-
-    DB.get(Date.today).class
-    # SELECT '2024-01-01' AS v LIMIT 1
-    String
-
-    DB.extension(:auto_cast_date_and_time)
-    DB.get(Date.today).class
-    # SELECT DATE '2024-01-01' AS v LIMIT 1
-    Date
-
-  This was already Sequel's default behavior on adapters that required
-  it.  This extension is usable on PostgreSQL and MySQL.  It is not
-  usable on SQLite (no date/time types) or Microsoft SQL Server (no
-  support for the SQL standard conversion syntax).
-
-  This extension can break code that currently works. If using it on
-  PostgreSQL, it will cast the values to TIMESTAMP, not TIMESTAMP
-  WITH TIME ZONE, which can break code that depended on an implicit
-  conversion to TIMESTAMP WITH TIME ZONE.  The pg_timestamptz
-  extension integrates with the the auto_cast_date_and_time extension
-  and will implicitly cast Time/DateTime to TIMESTAMP WITH TIME ZONE.
-
-* The sqlite adapter now supports a :cached value for the
-  :setup_regexp_function Database option, which will cache regexp
-  values instead of creating a new regexp per value to compare.  This
-  is much faster when using a regexp comparison on a large dataset,
-  but can result in a memory leak if using dynamic regexps. You can
-  also provide a Proc value for the :setup_regexp_function option,
-  which will be passed both the regexp source string and the database
-  string to compare, and should return whether the database string
-  matches the regexp string.
-
-* The rcte_tree plugin now supports a :union_all option, which can
-  be set to false to use UNION instead of UNION ALL in the recursive
-  common table expression.
-
-= Other Improvements
-
-* Time/DateTime/SQLTime literalization speed has more than doubled
-  compared to the previous version.  The internal code is also much
-  simpler, as the speedup resulted from removing multiple abstraction
-  layers that mostly existed for Ruby 1.8 support.
-
-* Database#table_exists? on PostgreSQL now handles lock or statement
-  timeout errors as evidence the table exists.
-
-* The round_timestamps extension now correctly rounds SQLTime values
-  on Microsoft SQL Server (the only database Sequel supports where
-  time precision is different than timestamp precision).
-
-* Fractional times and timestamps are now supported on SQLAnywhere,
-  except for time values when using the jdbc adapter due to a
-  limitation in the JDBC sqlanywhere driver.
-
-* Database#tables and #views on PostgreSQL now supports
-  SQL::Identifier values for the :schema option.
-
-* The named_timezones extension now works around a bug in DateTime.jd
-  on JRuby.
-
-= Backwards Compatibility
-
-* Time/DateTime/SQLTime literalization internals have changed.
-  If you are using an external adapter and the external adapter
-  overrides or calls any of the following methods:
-
-  * requires_sql_standard_datetimes?
-  * supports_timestamp_usecs?
-  * supports_timestamp_timezones?
-  * timestamp_precision
-  * sqltime_precision
-
-  then the adapter may need to be updated to support Sequel 5.76.0.
-  Additionally, if the adapter uses %N or %z in
-  default_timestamp_format, it may need to be updated. Adapters
-  should now just override default_timestamp_format and/or
-  default_time_format methods as appropriate for the database.
-
-* The Dataset#format_timestamp_offset private method has been
-  removed.

data/doc/release_notes/5.77.0.txt

@@ -1,63 +0,0 @@
-= New Features
-
-* A transaction_connection_validator extension has been added.  This
-  extension allows for transparently switching to a new connection if
-  a disconnect error is raised while trying to start a transaction, as
-  long as a connection was not already checked out from the pool
-  when the transaction method was called.  Transparent reconnection
-  is safe in this case, since no user code is retried.
-
-  This extension can have lower overhead than the
-  connection_validator extension if that is configured to check for
-  validity more often than the default of one hour.  However, it
-  only handles cases where transactions are used.  It can detect
-  disconnects that would not be detected by default with the
-  connection_validator extension, since that extension defaults to
-  only checking validity if the connection has not been used in the
-  last hour.
-
-* Sequel now supports a create_table :without_rowid option on SQLite,
-  to create a table WITHOUT ROWID, for better performance in some
-  cases. Users are encouraged to read the SQLite documentation on
-  WITHOUT ROWID before using this option.
-
-* The sqlite adapter now supports a :regexp_function_cache option, if
-  the :setup_regexp_function option is set to :cached.  The
-  :regexp_function_cache option should be a Proc (returning a cache
-  object to use), or a class.  It's possible to use
-  ObjectSpace::WeakKeyMap as the value of the option on Ruby 3.3+
-  to avoid the memory leaks that are possible when using
-  :setup_regexp_function option :cached value with dynamic regexps.
-
-* The duplicate_columns_handler extension now supports specifying
-  the on_duplicate_columns option as a connection string parameter.
-
-= Other Improvements
-
-* The list plugin now honors the :top option for the position when
-  adding the first item to the list, instead of always using 1.
-
-* Regexp matches on SQLite are now faster on Ruby 2.4+, using
-  Regexp#match?.
-
-* The uniqueness validation in the validation_helpers plugin now
-  uses empty? instead of count == 0, for better performance.
-
-* On Ruby 3.4+, Sequel uses the timed_queue connection pool instead
-  of the threaded connection pool by default.  This should make it
-  so no existing applications are affected by the default switch.
-  This should hopefully allow ample testing of the timed_queue
-  connection pool.  At some point in the future, if no problems
-  are repoted, Sequel will likely switch to using the timed_queue
-  connection pool by default on Ruby 3.2+.
-
-= Backwards Compatibility
-
-* Sequel now warns by default if using eager_graph/association_join
-  with an association that uses a block, in the cases where the
-  block would be ignored and there are no appropriate graph options
-  set. In Sequel 6, this warning will be turned into an exception.
-  It is recommended that users use the auto_restrict_eager_graph
-  plugin to turn this into an exception now, or use the
-  :graph_use_association_block option so that the block is not
-  ignored when graphing.

data/doc/release_notes/5.78.0.txt

@@ -1,67 +0,0 @@
-= New Features
-
-* SQLite 3.45+ jsonb functions are now supported in the sqlite_json_ops
-  extension.  Similar to the postgres_json_ops extension, there are
-  now separate methods for dealing with json and jsonb types:
-
-    Sequel.sqlite_json_op(:column)  # json
-    Sequel.sqlite_jsonb_op(:column) # jsonb
-
-  Some methods that use json_* functions for json ops use jsonb_*
-  functions for jsonb ops:
-
-    jb = Sequel.sqlite_jsonb_op(:column)
-    jb.extract('$.a')    # jsonb_extract(column, '$.a')
-    jb.insert('$.a', 1)  # jsonb_insert(column, '$.a', 1)
-    jb.set('$.a', 1)     # jsonb_set(column, '$.a', 1)
-    jb.replace('$.a', 1) # jsonb_replace(column, '$.a', 1)
-    jb.remove('$.a')     # jsonb_remove(column, '$.a')
-    jb.patch('{"a":2}')  # jsonb_patch(column, '{"a":2}')
-
-  You can use the json and jsonb methods to convert jsonb to json
-  and json to jsonb, respectively.
-
-    jb.json              # json(column)
-
-  Use of the json method on jsonb types is important, because if you
-  want to be able to deal with the values in Ruby, you must convert
-  the jsonb value to json in the database before the database returns
-  the value.  Unlike PostgreSQL, SQLite will not convert the value
-  from jsonb to json on retrieval, and direct use of SQLite's jsonb
-  format is unsupported by SQLite as it is subject to change.
-
-* Database#with_advisory_lock is now supported on PostgreSQL, MySQL,
-  and Microsoft SQL Server. This supports advisory (explicit)
-  locking, using the database-specific APIs.  To work on all three
-  servers, lock ids should be integers in the signed 64-bit range.
-
-    DB.with_advisory_lock(1234) do
-      # do something
-    end
-
-  By default, an AdvisoryLockError is raised if the lock cannot be
-  immediately acquired.  You can use the :wait option to wait until
-  the lock can be acquired, instead of raising.
-
-    DB.with_advisory_lock(1234, wait: true) do
-      # do something
-    end
-
-* Migrator.run now supports a :use_advisory_lock option to use
-  advisory locks when running migrations, so that it does not
-  attempt to run the same migration more than once in the case
-  where multiple processes are running the migrator simultaneously.
-  It's probably best to avoid running the migrator in multiple
-  processes simultaneously instead of relying on this option.
-
-= Other Improvements
-
-* Database#values now supports chaining with compounds on
-  PostgreSQL.
-
-    DB.values([[1, 2]]).union(DB.values([[3, 4]]))
-    # SELECT * FROM (VALUES (1, 2) UNION (VALUES (3, 4))) AS t1
-
-* The internal hash used to store transaction metadata now uses
-  compare_by_identity, which is faster and avoids potential
-  issues if a driver implements connection object equality.

data/doc/release_notes/5.79.0.txt

@@ -1,28 +0,0 @@
-= New Features
-
-* Dataset#select_prepend has been added for prepending to the
-  currently selected columns:
-
-    DB[:table].select_prepend(:column)
-    # SELECT column, table.*
-
-  As not all databases support "SELECT column, *", select_prepend
-  qualifies wildcard selections to all tables referenced in the
-  query.
-
-  The only reason to use select_prepend is if you want the hashes
-  returned by Sequel to be in a specific order.  Otherwise, it is
-  better to use select_append.
-
-* On PostgreSQL, Sequel now supports an :unlogged_tables_default
-  Database option, which will default created tables to be UNLOGGED.
-  This can be useful to speedup testing in some cases, but it should
-  never be used in cases where data integrity is important.
-
-= Other Improvements
-
-* On PostgreSQL, Database#create_or_replace_view now supports the
-  :materialized option.  This allows for dropping an existing
-  materialized view and creating a new one with the same name
-  (PostgreSQL does not have native support for replacing materialized
-  views).

data/doc/release_notes/5.8.0.txt

@@ -1,170 +0,0 @@
-= New Features
-
-* A pg_auto_constraint_validations plugin has been added, which
-  automatically converts many constraint violations raised as
-  exceptions to ValidationFailed exceptions when saving a model
-  instance.
-
-  The following constraint violation types are recognized and
-  supported:
-
-  * NOT NULL
-  * CHECK
-  * UNIQUE (except expression/functional indexes)
-  * FOREIGN KEY (both referencing and referenced by)
-
-  In the cases where the plugin cannot determine an appropriate
-  validation failure for the constraint violation, it just
-  reraises the original exception.
-
-  This plugin is not intended as a replacement for other validations,
-  it is intended as a last resort.  The purpose of validations is to
-  provide nice error messages for the user, and the error messages
-  generated by this plugin are fairly generic.  The error messages can
-  be customized using the :messages plugin option, but there is only a
-  single message used per constraint type.
-
-* Database#check_constraints has been added on PostgreSQL.  This
-  returns metadata related to each check constraint on a table:
-
-    DB.create_table(:foo) do
-      Integer :i
-      Integer :j
-      constraint(:ic, Sequel[:i] > 2)
-      constraint(:jc, Sequel[:j] > 2)
-      constraint(:ijc, Sequel[:i] - Sequel[:j] > 2)
-    end
-    DB.check_constraints(:foo)
-    # => {
-    #  :ic=>{:definition=>"CHECK ((i > 2))", :columns=>[:i]},
-    #  :jc=>{:definition=>"CHECK ((j > 2))", :columns=>[:j]},
-    #  :ijc=>{:definition=>"CHECK (((i - j) > 2))", :columns=>[:i, :j]}
-    # }
-
-* Database#foreign_key_list now supports a :reverse option on
-  PostgreSQL, which returns foreign keys referencing the given table,
-  instead of of foreign keys in the given table referencing other
-  tables:
-
-    DB.create_table!(:a) do
-      primary_key :id
-      Integer :i
-      Integer :j
-      foreign_key :a_id, :a, :foreign_key_constraint_name=>:a_a
-      unique [:i, :j]
-    end
-    DB.create_table!(:b) do
-      foreign_key :a_id, :a, :foreign_key_constraint_name=>:a_a
-      Integer :c
-      Integer :d
-      foreign_key [:c, :d], :a, :key=>[:j, :i], :name=>:a_c_d
-    end
-    DB.foreign_key_list(:a, :reverse=>true)
-    # => [
-    #  {:name=>:a_a, :columns=>[:a_id], :key=>[:id], :on_update=>:no_action,
-    #   :on_delete=>:no_action, :deferrable=>false, :table=>:a, :schema=>:public},
-    #  {:name=>:a_a, :columns=>[:a_id], :key=>[:id], :on_update=>:no_action,
-    #   :on_delete=>:no_action, :deferrable=>false, :table=>:b, :schema=>:public},
-    #  {:name=>:a_c_d, :columns=>[:c, :d], :key=>[:j, :i], :on_update=>:no_action,
-    #   :on_delete=>:no_action, :deferrable=>false, :table=>:b, :schema=>:public}
-    # ]
-
-* Dataset#nowait has been added, which will make the query fail
-  with a Sequel::DatabaseLockTimeout exception if it encounters
-  a locked row, overriding the default database behavior that
-  would wait until the lock was released. This method is supported
-  on PostgreSQL, Microsoft SQL Server, Oracle, and MySQL 8+.
-
-* Database#indexes now supports an :include_partial option on
-  PostgreSQL, which will include partial indexes in the output (Sequel
-  by default excludes partial indexes).
-
-* Common table expressions and window functions are now supported when
-  using MySQL 8+.
-
-* Dataset#skip_locked is now supported on MySQL 8+.
-
-* The connection_expiration extension now supports a
-  Database#connection_expiration_random_delay attribute, which is used
-  to randomize the expiration times, avoiding the thundering herd
-  problem.
-
-* The pg_enum extension now supports a rename_enum method for renaming
-  existing enum types.
-
-* Database#error_info on PostgreSQL now returns much more metadata
-  regarding the error.
-
-= Other Improvements
-
-* The dataset returned by the following dataset methods is cached,
-  which can improve performance significantly in certain cases:
-
-  * #distinct (without arguments or block)
-  * #from_self (without options)
-  * #lateral
-  * #qualify (without argument)
-  * #returning (without arguments)
-  * #select_all (without arguments)
-
-* If the primary_key serial: true, type: :serial, or type: :bigserial
-  options are given on PostgreSQL 10.2+, use a serial primary key
-  instead of an identity primary key.  This change was included in
-  Sequel 5.7.1.
-
-* The :search_path Database option is now supported as a shard
-  option on PostgreSQL, so different shards can use different
-  search paths.
-
-* The correct column order in Database#foreign_key_list on MySQL is
-  now forced, fixing issues on MySQL 8+.
-
-* When using case sensitive regexp matches on MySQL 8+, Sequel now
-  uses the REGEXP_LIKE function instead of the REGEXP BINARY
-  operator, to work around what appears to be a bug in MySQL 8+
-  related to the change in MySQL's regexp engine.
-
-* On MySQL 5.7+, the :extended option to Dataset#explain is now
-  ignored, since the :extended option's behavior in previous
-  MySQL versions is now the default behavior.
-
-* The MySQL HY000 generic SQL state error code is now ignored
-  in the mysql2 adapter, so it falls back to using the more
-  accurate backup error mapping in that case.
-
-* The pg_enum extension's schema modification methods now work
-  correctly if the Database instance is frozen.
-
-* The tactical_eager_loading plugin now respects the :allow_eager
-  association option, and will not attempt to eagerly load
-  associations when :allow_eager is false.
-
-* Using multiple add_constraint calls and a set_column_null call in
-  the same alter_table block on SQLite now works correctly.  Note
-  that if you are planning on ever modifying existing tables beyond
-  adding columns, you should probably choose a database that natively
-  supports such modification (SQLite does not).
-
-* Hashes returned by Database#foreign_key_list on PostgreSQL now
-  include a :schema entry, unless the support has been enabled
-  to make the :table entry be a qualified identifier.
-
-* Dataset#support_cte?(:insert) no longer returns true on
-  SQLAnywhere.  SQLAnywhere only supports common table
-  expressions for INSERT ... SELECT, not for all INSERT
-  statements. INSERT ... WITH ... SELECT is already
-  supported in Sequel using:
-
-    DB[:t1].insert(DB[:t2].with(DB[:t3]))
-
-* Model#_valid? is no longer made a public method in the
-  error_splitter plugin.
-
-= Backwards Compatibility
-
-* Calling the filter method on a proxy object returned by the
-  association_proxies plugin now warns on ruby <2.6.  This is
-  because starting in ruby 2.6, the behavior will change and the
-  method will be called on the array of associated objects
-  instead of on the dataset, as Enumerable#filter is being added
-  in ruby 2.6.

data/doc/release_notes/5.80.0.txt

@@ -1,40 +0,0 @@
-= New Features
-
-* A provenance dataset extension has been added. This extension makes
-  SQL queries include a comment describing how the dataset was built.
-  This can make debugging complex cases significantly easier. Here's
-  a simple example:
-
-    DB.extension :provenance
-
-    DB[:table].
-      select(:a).
-      where{b > 10}.
-      order(:c).
-      limit(10)
-      # SQL:
-      # SELECT a FROM table WHERE (b > 10) ORDER BY c LIMIT 10 --
-      #  -- Dataset Provenance
-      #  -- Keys:[:from] Source:(eval at bin/sequel:257):2:in `<main>'
-      #  -- Keys:[:select] Source:(eval at bin/sequel:257):3:in `<main>'
-      #  -- Keys:[:where] Source:(eval at bin/sequel:257):4:in `<main>'
-      #  -- Keys:[:order] Source:(eval at bin/sequel:257):5:in `<main>'
-      #  -- Keys:[:limit] Source:(eval at bin/sequel:257):6:in `<main>'
-
-  With the above example, it's obvious how the dataset is created, but
-  but in real applications, where datasets can be built from multiple
-  files, seeing where each dataset clone was made can be helpful.
-
-  The source listed will skip locations in the Ruby standard library
-  as well as Sequel itself.  Other locations can be skipped by
-  providing a Database :provenance_caller_ignore Regexp option:
-
-    DB.opts[:provenance_caller_ignore] = /\/gems\/library_name-/
-
-= Other Improvements
-
-* For dataset methods where Sequel can determine that the return
-  value would be equivalent to the receiver, Sequel now returns the
-  receiver.  This reduces the number of dataset allocations.
-
-* Sequel now supports Dataset#skip_locked on MariaDB 10.6+.