pkgsrc/databases/ruby-activerecord32/DESCR

= Active Record -- Object-relational mapping put on rails

Active Record connects classes to relational database tables to establish an
almost zero-configuration persistence layer for applications. The library
provides a base class that, when subclassed, sets up a mapping between the new
class and an existing table in the database. In context of an application,
these classes are commonly referred to as *models*. Models can also be
connected to other models; this is done by defining *associations*.
Importing ruby-activerecord32 3.2.2. ## Rails 3.2.1 (January 26, 2012) ## * The threshold for auto EXPLAIN is ignored if there's no logger. fxn * Call `to_s` on the value passed to `table_name=`, in particular symbols are supported (regression). Sergey Nartimov * Fix possible race condition when two threads try to define attribute methods for the same class. Jon Leighton ## Rails 3.2.0 (January 20, 2012) ## * Added a `with_lock` method to ActiveRecord objects, which starts a transaction, locks the object (pessimistically) and yields to the block. The method takes one (optional) parameter and passes it to `lock!`. Before: class Order < ActiveRecord::Base def cancel! transaction do lock! # ... cancelling logic end end end After: class Order < ActiveRecord::Base def cancel! with_lock do # ... cancelling logic end end end Olek Janiszewski * 'on' and 'ON' boolean columns values are type casted to true Santiago Pastorino * Added ability to run migrations only for given scope, which allows to run migrations only from one engine (for example to revert changes from engine that you want to remove). Example: rake db:migrate SCOPE=blog Piotr Sarnacki * Migrations copied from engines are now scoped with engine's name, for example 01_create_posts.blog.rb. Piotr Sarnacki * Implements `AR::Base.silence_auto_explain`. This method allows the user to selectively disable automatic EXPLAINs within a block. fxn * Implements automatic EXPLAIN logging for slow queries. A new configuration parameter `config.active_record.auto_explain_threshold_in_seconds` determines what's to be considered a slow query. Setting that to `nil` disables this feature. Defaults are 0.5 in development mode, and `nil` in test and production modes. As of this writing there's support for SQLite, MySQL (mysql2 adapter), and PostgreSQL. fxn * Implemented ActiveRecord::Relation#pluck method Method returns Array of column value from table under ActiveRecord model Client.pluck(:id) Bogdan Gusiev * Automatic closure of connections in threads is deprecated. For example the following code is deprecated: Thread.new { Post.find(1) }.join It should be changed to close the database connection at the end of the thread: Thread.new { Post.find(1) Post.connection.close }.join Only people who spawn threads in their application code need to worry about this change. * Deprecated: * `set_table_name` * `set_inheritance_column` * `set_sequence_name` * `set_primary_key` * `set_locking_column` Use an assignment method instead. For example, instead of `set_table_name`, use `self.table_name=`: class Project < ActiveRecord::Base self.table_name = "project" end Or define your own `self.table_name` method: class Post < ActiveRecord::Base def self.table_name "special_" + super end end Post.table_name # => "special_posts" Jon Leighton * Generated association methods are created within a separate module to allow overriding and composition using `super`. For a class named `MyModel`, the module is named `MyModel::GeneratedFeatureMethods`. It is included into the model class immediately after the `generated_attributes_methods` module defined in ActiveModel, so association methods override attribute methods of the same name. Josh Susser * Implemented ActiveRecord::Relation#explain. fxn * Add ActiveRecord::Relation#uniq for generating unique queries. Before: Client.select('DISTINCT name') After: Client.select(:name).uniq This also allows you to revert the unqueness in a relation: Client.select(:name).uniq.uniq(false) Jon Leighton * Support index sort order in sqlite, mysql and postgres adapters. Vlad Jebelev * Allow the :class_name option for associations to take a symbol (:Client) in addition to a string ('Client'). This is to avoid confusing newbies, and to be consistent with the fact that other options like :foreign_key already allow a symbol or a string. Jon Leighton * In development mode the db:drop task also drops the test database. For symmetry with the db:create task. Dmitriy Kiriyenko * Added ActiveRecord::Base.store for declaring simple single-column key/value stores DHH class User < ActiveRecord::Base store :settings, accessors: [ :color, :homepage ] end u = User.new(color: 'black', homepage: '37signals.com') u.color # Accessor stored attribute u.settings[:country] = 'Denmark' # Any attribute, even if not specified with an accessor * MySQL: case-insensitive uniqueness validation avoids calling LOWER when the column already uses a case-insensitive collation. Fixes #561. Joseph Palermo * Transactional fixtures enlist all active database connections. You can test models on different connections without disabling transactional fixtures. Jeremy Kemper * Add first_or_create, first_or_create!, first_or_initialize methods to Active Record. This is a better approach over the old find_or_create_by dynamic methods because it's clearer which arguments are used to find the record and which are used to create it: User.where(:first_name => "Scarlett").first_or_create!(:last_name => "Johansson") Andrés Mejía * Fix nested attributes bug where _destroy parameter is taken into account during :reject_if => :all_blank (fixes #2937) Aaron Christy * Add ActiveSupport::Cache::NullStore for use in development and testing. Brian Durand 2012-03-18 07:49:06 +01:00			`= Active Record -- Object-relational mapping put on rails`

			`Active Record connects classes to relational database tables to establish an`
			`almost zero-configuration persistence layer for applications. The library`
			`provides a base class that, when subclassed, sets up a mapping between the new`
			`class and an existing table in the database. In context of an application,`
			`these classes are commonly referred to as models. Models can also be`
			`connected to other models; this is done by defining associations.`