sequel 5.6.0 → 5.7.0

data/doc/release_notes/3.38.0.txt

@@ -1,234 +0,0 @@
-= New Features
-
-* A pg_row extension has been added that supports PostgreSQL's
-  row-valued/composite types.  You can register support for
-  specific row types:
-
-    DB.register_row_type(:address)
-
-  Then you can create values of that row type:
-
-    ad = DB.row_type(:address, ['555 Foo St.', 'Bar City', '98765'])
-    # or
-    ad = DB.row_type(:address, :street=>'555 Foo St.',
-                          :city=>'Bar City', :zip=>'98765')
-
-  Which you can use in your datasets:
-
-    DB[:people].insert(:name=>'Me', :address=>ad)
-  
-  If you are using the native postgres adapter, when retreiving
-  row type values, they will be returned as instances of the row
-  type, which are hash-like objects:
-
-    ad = DB[:people].get(:address)
-    ad[:street] # => '555 Foo St.'
-    ad[:city]   # => 'Bar City'
-    ad[:zip]    # => '98765'
-
-  If you are also using the pg_array extension, then arrays of
-  composite types are supported automatically.  Composite
-  types can also include arrays of other types as well as other
-  composite types, though recursive composite types are not
-  allowed by PostgreSQL.
-
-  Using arrays and composite types brings one of the benefits
-  of document databases to PostgreSQL, allowing you to store
-  nested structures inside a single row.
-
-* A pg_row_ops extension has been added that adds DSL support
-  for accessing members of row-valued/composite types. You
-  first create a row op:
-
-    r = Sequel.pg_row_op(:row_column)
-
-  Then you can get DSL support for accessing members of that
-  row_column via the #[] method:
-
-    r[:a] # (row_column).a
-
-  This works with composite types containing composite types:
-
-    r[:a][:b] # ((row_column).a).b
-
-  When used in conjunction with the pg_array_ops extension,
-  there is support for composite types that include arrays,
-  as well as arrays of composite types:
-
-    r[1][:a] # (row_column[1]).a
-    r[:a][1] # (row_column).a[1]
-
-  The extension offers additional support for referencing
-  a table's type when it contains a column with the same
-  name, see the RDoc for details.
-
-* A pg_row plugin has been added, that works with the pg_row
-  extension, and allows you to represent row-valued types as
-  Sequel::Model objects (instead of the hash-like objects
-  they use by default).  In your model class, you load the
-  plugin:
-
-    class Address < Sequel::Model(:address)
-      plugin :pg_row
-    end
-
-  Then you can use Address instances in your datasets:
-  
-    ad = Address.new(:street=>'555 Foo St.',
-                     :city=>'Bar City', :zip=>'98765')
-    DB[:people].insert(:name=>'Me', :address=>ad)
-
-  And if you are using the native postgres adapter, the dataset
-  will return the type as a model instance:
-
-    ad = DB[:people].get(:address)
-    ad.street # => '555 Foo St.'
-    ad.city   # => 'Bar City'
-    ad.zip    # => '98765'
- 
-* A pg_typecast_on_load plugin has been added.  This plugin is
-  designed for use with the jdbc/postgres, do/postgres, and
-  swift/postgres adapters, and it is similar to the
-  typecast_on_load plugin.  However, while the typecast_on_load
-  plugin uses setter methods, the pg_typecast_on_load plugin
-  uses the same code that the native postgres adapter uses for
-  typecasting.
-
-* The tinytds adapter now supports a :textsize option to override
-  the default TEXTSIZE setting.  The FreeTDS default is fairly
-  small (~64k), so if you want to use large blob or text columns,
-  you should probably set this to a value larger than the
-  largest text/blob you want to use.
-
-* Sequel.expr when called with a symbol now splits the symbol and
-  returns an Identifier, QualifiedIdentifier, or AliasedExpression, 
-  depending on the content of the symbol.  Previously, it only
-  wrapped the symbol using a Wrapper.
-
-* Identifier#* and QualifiedIdentifier#* when called without any
-  argument now represent a selection of all columns from the
-  represented table:
-
-    Sequel.expr(:table).*          # table.*
-    Sequel.expr(:schema__table).*  # schema.table.*
-
-  This makes it easier to represent the selection of all columns
-  in a table without using the core extensions.
-
-* Model#values now has a Model#to_hash alias.
-
-* SQL::Blob values now have as, cast, and lit methods even if the
-  core extensions are not loaded.
-
-= Other Improvements
-
-* When loading multiple pg_* extensions into a Database instance,
-  the conversion procs are only reset once instead of once per
-  extension.
-
-* All adapters that access PostgreSQL now store type conversion
-  procs, similar to the native postgres adapter.  This has been
-  added to make it easier to write extensions that support
-  advanced PostgreSQL types.
-
-* Database#schema output on PostgreSQL now includes the type oid
-  for each column.
-
-* You can now register custom array types to specific Database
-  instances, using the :type_procs and :typecast_methods_module
-  options, so it is now possible to have custom array types
-  without affecting global state.
-
-* Dropping of columns with defaults now works correctly on
-  Microsoft SQL Server.  Before, it would fail as the related
-  constraint was not dropped first.
-
-* The MySQL type "double(x,y)" is now recognized as a float type.
-
-* The jdbc/jtds and jdbc/derby adapters now handle nil prepared
-  statement values in more cases.
-
-* Blob prepared statement arguments are now handled correctly on
-  jdbc/db2 and jdbc/oracle.
-
-* Sequel now works around a Time#nsec bug in JRuby 1.6 ruby 1.9 mode
-  when using Time values in prepared statements in the jdbc adapter.
-
-* Java::JavaUtil::UUID types are now returned as ruby strings
-  when converting types in the jdbc adapter.
-
-* Real boolean literals are now used on derby 10.7+.  On derby <10.7
-  Sequel still uses (1 = 1) and (1 != 1) for true and false.  This
-  allows you to use boolean columns with a true/false default on
-  derby 10.7+.
-
-* Clobs are now treated as string types instead of blobs on derby,
-  since treating clob as blob doesn't work there.
-
-* The swift adapter now supports an output identifier method.
-
-* The swift adapter now returns blobs as SQL::Blob instances.
-
-* The schema_dumper extension no longer produces code that requires
-  the core extensions.
-
-* All of Sequel's specs now run without the core extensions loaded,
-  ensuring that none of the internals depend on the core extensions.
-  The only exception is the specs for the core extensions themselves.
-
-= Backwards Compatibility
-
-* The pg_* extensions no longer modify core classes if the
-  core_extensions extension is not loaded.  All methods they added now
-  have equivalent methods on the main Sequel module:
-
-    Sequel.pg_array
-    Sequel.pg_array_op
-    Sequel.hstore
-    Sequel.hstore_op
-    Sequel.pg_json
-    Sequel.pg_range
-    Sequel.pg_range_op
-
-* The Sequel::SQL::IdentifierMethods module has been removed.  This
-  module was only included in Symbol if the core_extensions were
-  enabled.  Since it only defined a single method, now the core
-  extensions just define that method directly on Symbol.
-
-* The swift adapter now requires swift-db-{postgres,mysql,sqlite3}
-  gems instead of the swift gem.  swift/postgres requires
-  swift-db-postgres 0.2.0+, swift/sqlite requires swift-db-sqlite
-  0.1.2+, and swift/mysql requires swift-db-mysql.
-
-* Sequel will no longer typecast a string to a PostgreSQL array
-  or hstore column in a model column setter.  This is because the
-  parsers that Sequel uses were designed to support only
-  PostgreSQL's output format.  It's unlikely that a user would
-  provide that format for typecasting, and while there aren't known
-  security issues with the parsers, they were not designed to handle
-  arbtirary user input, so typecasting from string is no longer
-  allowed and will now raise an error.
-
-  The only reason such typecasting was allowed in the first place
-  was to work around issues in the jdbc/postgres, do/postgres, and
-  swift/postgres adapters, using the the typecast_on_load plugin.
-  If you were previously using the typecast_on_load plugin for
-  hstore or array columns, you need to switch to using the new
-  pg_typecast_on_load plugin.
-
-* The private get_conversion_procs method in the postgres adapter
-  no longer accepts an argument.
-
-* The Sequel::Postgres::PGArray::DatabaseMethods singleton
-  define_array_typecast_method method has been removed.  This
-  method was designed for internal use.
-
-* The change to make Sequel.expr split symbols can cause the
-  following type of code to break:
-
-    Sequel.expr(:column___alias).desc
-
-  This is because expr now returns an AliasedExpression, which
-  doesn't support the desc method.  However, as you can't
-  apply an order to an aliased expression, nobody should be
-  relying on this.

data/doc/release_notes/3.39.0.txt

@@ -1,237 +0,0 @@
-= New Features
-
-* A constraint_validations extension and plugin have been added,
-  which allow you to define validations when creating tables,
-  which are enforced by database constraints, and have those
-  validations be automatically discovered and used by your
-  Sequel::Model classes.
-
-  The extension is designed to be used in your migrations/schema
-  modification code:
-
-    DB.extension(:constraint_validations)
-    DB.create_constraint_validations_table
-    DB.create_table(:foos) do
-      primary_key :id
-      String :name
-
-      validate do
-        min_length 5, :name
-      end
-    end
-
-  This creates a database CHECK constraint that ensures that the
-  minimum length for the column is 5 characters.  It also adds
-  metadata about the validation to the
-  sequel_constraint_validations table.
-
-  To have the model class automatically create validations, just
-  include the plugin in the model:
-
-    class Foo < Sequel::Model
-      plugin :constraint_validations
-    end
-
-  Note that MySQL does not enforce CHECK constraints (it parses
-  but ignores them), so using the extension on MySQL does not
-  actually enforce constraints at the database level, though it
-  still does support the automatic model validations if the plugin
-  is used.
-
-* Dataset#count now takes an argument or a virtual row block,
-  allowing you to do:
-
-    DB[:table].count(:column_name)
-    DB[:table].count{function_name(column1, column2)}
-
-  When count is given an argument, instead of returning the total
-  number of rows, it returns the number of rows where the
-  argument has a non-NULL value.
-
-* Database#copy_into has been added to the postgres adapter when
-  the pg driver is being used, and can be used for very fast
-  inserts into tables if you already have the input preformatted
-  in PostgreSQL text or CSV format.
-
-* set_table_not_null has been added to the alter table generator,
-  for a nicer API:
-
-    alter_table(:t){set_column_not_null :col}
-    # instead of
-    alter_table(:t){set_column_allow_null :col, false}
-
-  Additionally, set_column_allow_null now defaults the second
-  argument to true for a nicer API:
-
-    alter_table(:t){set_column_allow_null :col}
-    # instead of
-    alter_table(:t){set_column_allow_null :col, true}
-
-* Database#supports_regexp? has been added for checking if the
-  database supports Regexp in filters.  Currently, only MySQL and
-  PostgreSQL support Regexps.
-
-  Attempting to use a Regexp on a database that doesn't support it
-  now raises an error when attempting to generate the SQL, instead
-  of sending invalid SQL to the database.
-
-* Sequel.char_length has been added for a cross platform
-  char_length function (emulated when char_length is not supported
-  natively by the database).
-
-* Sequel.trim has been added for a cross platform trim function
-  (emulated when trim is not supported natively by the database).
-
-* ValidationFailed and HookFailed exceptions now have a model method
-  that returns the model instance related to the exception.  This
-  makes it possible to use Model.create inside a begin/rescue block
-  and get access to the underlying instance if there is a validation
-  or before/around hook error.
-
-* The subclasses plugin now accepts a block, which is called with
-  each model class created.  This is useful if you want to apply
-  changes to classes created in the future instead of just existing
-  classes.
-
-* The validates_unique validation in the validation_helpers plugin
-  now accepts a :where option for a custom uniqueness filter.  Among
-  other things this makes it easy to implement a case insensitive
-  uniqueness validation on a case sensitive column.
-
-* The threaded connection pools now support a
-  :connection_handling=>:disconnect option, which makes them disconnect
-  connections after use instead of returning them to the pool.  This
-  makes it possible to completely control connection lifetime using
-  Database#synchronize.
-
-* The pg_row_op extension now has support for PGRowOp#*, for referencing
-  the members of the composite type as separate columns.
-
-* MySQL's set type and default value are now recognized.
-
-* bin/sequel now accepts a -c argument for running an arbitrary
-  code string instead of using an IRB prompt.
-
-= Other Improvements
-
-* Sequel now parses current date/timestamp column defaults when
-  parsing the schema for a table.  The values will be returned
-  as Sequel::CURRENT_DATE for date columns and
-  Sequel::CURRENT_TIMESTAMP for timestamp columns.
-
-  The schema_dumper extension will work with these defaults, so
-  if you dump the schema for a table with a column that uses
-  a current timestamp default, the dumped schema will include
-  the default.
-
-  The defaults setter plugin also works with these changes, so
-  that when new model objects are instantiated, they get the
-  current Date/Time/DateTime values set.
-
-* On MySQL and PostgreSQL, Sequel will now by default attempt
-  to combine multiple alter_table operations into a single
-  query where it believes it can do so correctly.  This can
-  potentially improve performance ~N times, where N is the number
-  of alter table operations.
-
-  This can change the SQL used for old migrations (though it
-  shouldn't change the result), and is a potentially risky
-  change.  This may be disabled by default in future versions
-  if it causes problems.
-
-* The defaults_setter plugin now correctly sets false default
-  values.
-
-* The schema_dumper plugin now preserves fractional seconds
-  in timestamp column defaults when dumping.
-
-* Time->DateTime and DateTime->Time typecasts now retain
-  fractional seconds on ruby 1.8.
-
-* Array arguments passed to most PGArrayOp methods are now
-  automatically wrapped in a PGArray.  If you want to use this
-  support, you need to make sure to load both the pg_array
-  and pg_array_op extensions.
-
-* Sequel now does a better job of finding the sequence for a
-  given table on PostgreSQL, handling more corner cases.  A small
-  side effect of this is sometimes sequence names will be quoted.
-
-* Some potential thread-safety issues when using Sequel with
-  PostgreSQL on a non-GVL ruby implementation have been fixed.
-
-* Sequel now correctly caches the server version query on MySQL.
-
-* Sets of alter_table operations on MySQL and Microsoft SQL Server
-  that require parsing the current database schema, where later
-  alter_table operations depend on earlier ones, should now work
-  correctly.
-
-* You can now drop check constraints on tables on SQLite, though
-  doing so drops all check constraints on the table, not only the
-  specific check constraint given.
-
-* The identity_map plugin no longer breaks if used with a model
-  without a primary key.
-
-* Sequel::SQL::NegativeBooleanConstant now inherits from Constant
-  instead of BooleanConstant.  This means that
-
-    Sequel::NULL == Sequel::NOTNULL
-
-  is now false instead of true.
-
-* You can now override the convert_tinyint_to_bool settings on a
-  per-Dataset basis in the mysql and mysql2 adapters, though
-  the overriding is different depending on the adapter.  Check the
-  commit log for details.
-
-* timestamp(N) types are now recognized as datetime, which should
-  fix certain cases on Oracle.
-
-* Dataset#insert now handles a single model instance argument
-  as a single value if the model uses the pg_row plugin.
-
-* When joining a model dataset using a model class as the table
-  argument, a subselect is used unless the model is a simple select
-  from the underlying table.
-
-* The specs now cleanup after themselves, dropping the tables that
-  they create for testing.
-
-= Backwards Compatibility
-
-* The defaults_setter plugin's behavior changed due to the 
-  current date/timestamp support.  Previously, it would not set
-  a value for the column, since the default wasn't recognized.
-  Therefore, the database would use the default value on insert,
-  which would be the database's current timestamp.
-
-  Now, the value is set to the current Date/Time/DateTime on
-  model object instantiation, so the database wouldn't use the
-  column default.  Instead of the database's current timestamp
-  on insert, the column value will be the application's
-  current timestamp on model instantiation.
-
-  Users who don't want this behavior can remove the default values
-  in the model:
-
-    Model.default_values.delete(:column_name)
-
-* Plain (non-model) datasets no longer allow insert to accept
-  a single model instance argument.  Also, they no longer call
-  values on a single argument if the object responds to it.
-
-* Plain (non-model) datasets no longer accept model classes as
-  tables in the join/graph methods.  Also, they no longer call
-  table_name on the argument if the object responds to it.
-
-* The schema_dumper extension now requires the eval_inspect
-  extension, which changes inspect output for
-  Sequel::SQL::Expression objects.
-
-* Custom adapters that override Database#alter_table_sql_list now
-  need to make sure it returns an already flattened array.
-
-* The identity_map_key method in the identity_map plugin now returns
-  nil instead of a random string if the given pk is nil.