sequel 4.36.0 → 5.61.0

data/doc/release_notes/3.21.0.txt

@@ -1,87 +0,0 @@
-= New Features
-
-* A tinytds adapter was added, enabling Sequel users on a C-based
-  ruby running on *nix easy access to Microsoft SQL Server.
-  Previously, the best way to connect to Microsoft SQL Server from
-  a C-based ruby on *nix was to use the ODBC adapter with unixodbc
-  and freetds.  However, setting that up is nontrivial, while
-  setting up tinytds is very easy.
-  
-  Note that the tinytds adapter currently requires the git master
-  branch of tiny_tds, but tiny_tds 0.4.0 should include the related
-  changes.
-  
-* An association_autoreloading plugin has been added to Sequel,
-  which removes stale many_to_one associations from the cache when
-  the associated foreign key setter is used to change the value of
-  the foreign key.
-
-* bin/sequel now operates more like a standard *nix utility.
-  If given a file on the command line after the connection
-  string, it will assume that file has ruby code and load it.
-  If stdin is not a tty, it will read from stdin and execute it
-  as ruby code.
-  
-  For recent Linux users, this means you can have a shebang line
-  such as:
-  
-    #!/usr/bin/sequel postgres://user:pass@host/db
-    
-  to create a self contained script.
-
-* bin/sequel now supports -r and -I options similar to ruby's
-  -r and -I options.
-  
-* MySQL datasets now have a calc_found_rows method that uses
-  SQL_CALC_FOUND_ROWS, which provides a fast way to limit the
-  number of results returned by a dataset while having an easy
-  way to determine how many rows would have been returned if no
-  limit was applied.
-
-= Other Improvements
-
-* The Sequel::Model.plugin method can now be overridden just like
-  any other method.  Previously, it was the only method that
-  was defined directly on the class.  This allows the creation
-  of plugins that can modify the plugin system itself.
-
-* Symbol splitting (:table__column___alias) now works correctly
-  for identifiers that include characters that aren't in [\w ].
-  Among other things, this means that identifiers with accented
-  characters or even kanji characters can be used with symbol
-  splitting.
-  
-* If cover? is defined, it is now used in preference to include?
-  for the validates_includes/validates_inclusion_of validations.
-  ruby 1.9 defines include? differently for some ranges and can
-  be very slow, while cover? is similar to the 1.8 behavior of
-  just checking the beginning and end of the range.
-  
-* The bin/sequel -L option now takes effect even if the -m,
-  -C, -d, or -D options are used.
-  
-* The schema_dumper extension now recognizes the "bigint unsigned"
-  type.
-  
-* On Microsoft SQL Server, if joining to a subselect that uses a
-  common table expression, that common table expression is
-  promoted to the main dataset.  This allows most queries to work
-  correctly, but is vulnerable to issues if both the current
-  dataset and the joined dataset use common table expressions with
-  the same name.  Unfortunately, unlike PostgreSQL, Microsoft SQL
-  Server does not allow common table expressions to occur in
-  subselects.
-
-* The NULL/NOT NULL, DEFAULT, and UNIQUE column options now
-  use the proper order on H2 and Oracle, so they can now be
-  used in conjunction with each other.
-  
-* Row locks are now enabled on Oracle.
-
-* The join_table method on MySQL no longer ignores the block it was
-  given.
-  
-* The informix adapter now supports ruby-informix version >= 0.7.3,
-  while still being backwards compatible with older versions.
-
-* The specs now run under both RSpec 2 and RSpec 1.

data/doc/release_notes/3.22.0.txt

@@ -1,39 +0,0 @@
-= New Features
-
-* Support COLLATE in column definitions.  At least MySQL and Microsoft
-  SQL Server support them, and PostgreSQL 9.1 should as well.
-
-* When connecting to Microsoft SQL Server, you can use the
-  mssql_unicode_strings accessor to turn of the default usage
-  of unicode strings (N'') and use regular strings (''). This
-  can improve performance, but changes the behavior.  It's
-  set to true by default for backwards compatibility.  You can
-  change it at both the dataset and database level:
-
-    DB.mssql_unicode_strings = false # default for datasets
-    dataset.mssql_unicode_strings = false # just this dataset
-
-* In the oracle adapter, if Sequel.application_timezone is :utc, set
-  the timezone for the connection to use the 00:00 timezone.
-
-= Other Improvements
-
-* In the single_table_inheritance plugin, correctly handle a
-  multi-level class hierarchy so that loading instances from a
-  middle level of the hierarchy can return instances of subclasses.
-
-* Don't use a schema when creating a temporary table, even if
-  default_schema is set.
-
-* Fix the migrator when a default_schema is used.
-
-* In the ado adapter, assume a connection to SQL Server if the
-  :conn_string is given and doesn't indicate Access/Jet.
-
-* Fix fetching rows in the tinytds adapter when the
-  identifier_output_method is nil.
-
-* The tinytds adapter now checks for disconnect errors, but it might
-  not be reliable until the next release of tiny_tds.
-
-* The odbc adapter now handles ODBC::Time instances correctly.

data/doc/release_notes/3.23.0.txt

@@ -1,172 +0,0 @@
-= New Features
-
-* Sequel now allows dynamic customization for eager loading.
-  Previously, the parameters for eager loading were fixed at
-  association creation time.  Now, they can be modified at query
-  time.  To dynamically modify an eager load, you use a hash with
-  the proc as the value. For example, if you have this code:
-
-    Artist.eager(:albums)
-
-  And you only want to eagerly load albums where the id is greater
-  than or equal to some number provided by the user, you do:
-
-    min = params[:min].to_i
-    Artist.eager(:albums=>proc{|ds| ds.where{id > min}})
-    
-  This also works when eager loading via eager_graph:
-  
-    Artist.eager_graph(:albums=>proc{|ds| ds.where{id > min}})
-  
-  For eager_graph, the dataset is the dataset to graph into the
-  current dataset, and filtering it will result in an SQL query
-  that joins to a subquery.
-  
-  You can also use dynamic customization while cascading to also
-  eagerly load dependent associations, by making the hash value
-  a single entry hash with a proc key and the value being the
-  dependent associations to eagerly load. For example, if you want
-  to eagerly load tracks for those albums:
-
-    Artist.eager(:albums=>{proc{|ds| ds.where{id > min}}=>:tracks})
-
-* Sequel also now allows dynamic customization for regular
-  association loading.  Previously, this was possible by using the
-  association's dataset:
-
-    albums = artist.albums_dataset.filter{id > min}
-
-  However, then there was no handling of caching, callbacks, or
-  reciprocals.  For example:
-
-    albums.each{|album| album.artist}
-    
-  Would issue one query per album to get the artist, because the
-  reciprocal association was not set.  Now you can provide a
-  block to the association method:
-  
-    albums = artist.albums{|ds| ds.filter{id > min}}
-    
-  This block is called with the dataset used to retrieve the
-  associated objects, and should return a modified version of that
-  dataset.
-  
-  Note that ruby 1.8.6 doesn't allow blocks to take block arguments,
-  so you have to pass the block as a separate proc argument to the
-  association method if you are still using 1.8.6.
-
-* Sequel now supports filtering by associations.  This wasn't
-  previously supported as filtering is a dataset level feature and
-  associations are a model level feature, and datasets do not depend
-  on models.  Now, model datasets have the ability to filter by
-  associations.  For example, to get all albums for a given artist,
-  you could do:
-  
-    artist = Artist[1]
-    Album.filter(:artist=>artist)
-    
-  Since the above can also be accomplished with:
-  
-    artist.albums
-    
-  this may not seem like a big improvement, but it allows you to
-  filter on multiple associations simultaneously:
-  
-    Album.filter(:artist=>artist, :publisher=>publisher)
-    
-  For simple many_to_one associations, the above is just a simpler
-  way to do:
-  
-    Album.filter(:artist_id=>artist.id, :publisher_id=>publisher.id)
-    
-  Sequel supports this for all association types, including
-  many_to_many and many_through_many, where a subquery is used, and
-  it also works when composite key associations are used:
-  
-    Album.filter(:artist=>artist, :tags=>tag)
-    
-  This will give you the albums for that artist that are also tagged
-  with that tag.  To provide multiple values for the same
-  association, mostly useful for many_to_many associations, you can
-  either use separate filter calls or specify the conditions as an
-  array:
-  
-    Album.filter(:tags=>tag1).filter(:tags=>tag2)
-    Album.filter([[:tags, tag1], [:tags, tag2]])
-
-* A columns_introspection extension has been added that makes
-  datasets attempt to guess their columns in some cases instead of
-  issuing a database query.  This can improve performance in cases
-  where the columns are needed implicitly, such as graphing.  After
-  loading the extension, you can enable the support for specific
-  datasets by extending them with Sequel::ColumnIntrospection.  To
-  enable introspection for all datasets, use:
-  
-    Sequel::Dataset.introspect_all_columns
-
-* A serialization_modification_detection plugin has been added.
-  Previously, Sequel could not detect modifications made to
-  serialized objects.  It could detect modification if you assigned
-  a new value:
-  
-    model.hash_column = model.hash_column.merge(:foo=>:bar)
-    
-  but not if you just modified the object directly:
-  
-    model.hash_columns[:foo] = :bar
-    
-  With this plugin, such modifications can be detected, at a
-  potentially significant performance cost.
-
-= Other Improvements
-
-* When using a migration directory containing both older integer
-  migrations and newer timestamp migrations, where some integer
-  migrations have not been applied, make sure to apply the remaining
-  integer migrations before the timestamp migrations.  Previously,
-  they could be applied out of order due to a lexicographic sort
-  being used instead of a numeric sort.
-
-* If a model does not select all columns from its table, the
-  insert_select optimization is no longer used.  Previously,
-  creating a new model object for such a model could result in the
-  object containing columns that the model does not select.
-
-* You can now use :select=>[] as an option for many_to_many
-  associations to select all columns from both the associated
-  table and the join table.  Previously, this raised an error and
-  required you do :select=>'*'.lit as a workaround.  The default
-  remains to select all columns in the associated table and none
-  from the join table.
-
-* The xml_serializer plugin now handles namespaced models by
-  using __ instead of / as the namespace separator.  Previously, /
-  was used and caused problems as it is not valid XML.
-  
-* The :eager_grapher association option can now accept a proc that
-  takes a single hash of options instead of a fixed 3 arguments.
-  This is the recommended way going forward of writing custom
-  :eager_graphers, and all of the internal ones have been converted.
-  The previous way of using 3 arguments is still supported.
-  
-* A bug in the identity_map plugin for many_to_one associations
-  without full association reflection information has been fixed.
-
-* Sequel is now using GitHub Issues for issue tracking.  Old issues
-  have been migrated from Google Code.
-
-= Backwards Compatibility
-
-* The filter by associations support breaks backward compatibilty for
-  users who previously added an sql_literal instance method to
-  Sequel::Model.  Usually, that was done to for reasons similar to
-  but inferior than the filter by association support.  The following
-  code can be used as a temporary workaround until you can modify
-  your program to use the new filter by associations support:
-  
-    Sequel::Model::Associations::DatasetMethods.
-      send(:remove_method, :complex_expression_sql)
-
-* The private Sequel::Model#_load_associated_objects method now takes
-  an additional, optional options hash.  Plugins that override that
-  method need to be modified.