Commit graph

8 commits

Author SHA1 Message Date
taca
2199771cbb Update ruby-activerecord3 to 3.0.14.
pkgsrc change: add RUBY_RAILS_STRICT_DEP which will be enabled later.

## Rails 3.0.14 (Jun 12, 2012)

*   protect against the nesting of hashes changing the
    table context in the next call to build_from_hash. This fix
    covers this case as well.

    CVE-2012-2695
2012-06-14 14:50:06 +00:00
taca
b71e99898b Update ruby-activerecord3 to 3.0.12.
pkgsrc change:
* Tweak COMMENT.

No changes except version.
2012-03-18 05:26:09 +00:00
taca
894225f3b0 * Switch to use RUBY_RAILS_SUPPORTED.
* Correct some dependency.

Bump PKGREVISION.
2011-12-13 15:50:06 +00:00
taca
968e47f445 Update ruby-activerecord3 pacakge to 3.0.8.
*Rails 3.0.8 (unreleased)*

* Fix various problems with using :primary_key and :foreign_key options in conjunction with
  :through associations. [Jon Leighton]

* Correctly handle inner joins on polymorphic relationships.

* Fixed infinity and negative infinity cases in PG date columns.

* Creating records with invalid associations via `create` or `save` will no
  longer raise exceptions.
2011-06-11 03:22:09 +00:00
taca
e7f00b2ac2 Update ruby-activerecord3 package to 3.0.5.
*Rails 3.0.5 (unreleased)*

* Model.where(:column => 1).where(:column => 2) will always produce an
  AND query.

  [Aaron Patterson]

* Deprecated support for interpolated association conditions in the
  form of :conditions => 'foo = #{bar}'.

  Instead, you should use a proc, like so:

  Before:

    has_many :things, :conditions => 'foo = #{bar}'

  After:

    has_many :things, :conditions => proc { "foo = #{bar}" }

  Inside the proc, 'self' is the object which is the owner of the
  association, unless you are eager loading the association, in which
  case 'self' is the class which the association is within.

  You can have any "normal" conditions inside the proc, so the
  following will work too:

    has_many :things, :conditions => proc { ["foo = ?", bar] }

  Previously :insert_sql and :delete_sql on has_and_belongs_to_many
  association allowed you to call 'record' to get the record being
  inserted or deleted. This is now passed as an argument to the proc.

  [Jon Leighton]
2011-03-23 14:48:12 +00:00
taca
19e2cf02b8 Update ruby-activerecord3 package to 3.0.4.
* More strict dependency reflect gemspec's description.


*Rails 3.0.4 (unreleased)*

* Added deprecation warning for has_and_belongs_to_many associations where the join table has
  additional attributes other than the keys. Access to these attributes is removed in 3.1.
  Please use has_many :through instead. [Jon Leighton]

*Rails 3.0.3 (November 16, 2010)*

* Support find by class like this: Post.where(:name => Post)


*Rails 3.0.2 (November 15, 2010)*

* Dramatic speed increase (see: http://engineering.attinteractive.com/2010/10/arel-two-point-ohhhhh-yaaaaaa/) [Aaron Patterson]

* reorder is deprecated in favor of except(:order).order(...) [Santiago Pastorino]

* except is now AR public API

    Model.order('name').except(:order).order('salary')

  generates:

    SELECT * FROM models ORDER BY salary

  [Santiago Pastorino]

* The following code:

    Model.limit(10).scoping { Model.count }

  now generates the following SQL:

    SELECT COUNT(*) FROM models LIMIT 10

  This may not return what you want.  Instead, you may with to do something
  like this:

    Model.limit(10).scoping { Model.all.size }

  [Aaron Patterson]
2011-02-09 13:00:07 +00:00
taca
169bf40e90 Update databases/ruby-activerecord3 to 3.0.1.
This release fixes CVE-2010-3933 security problem and it is part
of Rails 3.0.1.
2010-10-15 11:43:27 +00:00
taca
d450ca8e5e Importing databases/ruby-activerecord3 3.0.0.
= 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*.

(This is part of Ruby on Rails 3.)
2010-09-12 04:22:21 +00:00