Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Mar 12, 2012
  1. @pixeltrix

    Add dynamic find_or_create_by_{attribute}! method.

    pixeltrix authored
    (cherry picked from commit 5282485d310d1a6ffcf55e4e7f56ab234e16880d)
Commits on Mar 9, 2012
  1. @rafaelfranca

    Fix my name in the CHANGELOG to follow the convention

    rafaelfranca authored
    Also add missing entries and use the formating convention
Commits on Mar 8, 2012
  1. @vijaydev

    changelog updates [ci skip]

    vijaydev authored
Commits on Jan 26, 2012
  1. @fxn

    CHANGELOG revision for v3.2.1

    fxn authored
  2. @fxn

    registers 2483460 in the CHANGELOG

    fxn authored
Commits on Jan 20, 2012
  1. @jonleighton

    Fix another race condition.

    jonleighton authored
    From 2c667f6.
    Thanks @pwnall for the heads-up.
  2. @dhh

    Preparing for 3.2.0 release

    dhh authored
Commits on Jan 19, 2012
  1. @tenderlove

    Merge pull request #4531 from exviva/pessimistic_with_lock

    tenderlove authored
    Add ActiveRecord::Base#with_lock
Commits on Jan 12, 2012
  1. @spastorino

    Add CHANGELOG entry

    spastorino authored
Commits on Dec 12, 2011
  1. @bdurand

    Add ActiveSupport::Cache::NullStore to expose caching interface witho…

    bdurand authored
    …ut actually caching for development and test environments.
Commits on Dec 9, 2011
  1. @drogus

    Allow to run migrations with given scope, with SCOPE=<scope>

    drogus authored
    Scope in migrations can be defined by adding suffix in filename,
    like: Such migration have blog scope.
    Scope is automatically added while copying migrations from engine,
    so if you want to revert all of the migrations from given engine,
    you can just run db:migrate with SCOPE, like:
        rake db:migrate SCOPE=blog
Commits on Dec 3, 2011
  1. @fxn

    removes the convenience instance version of AR::Base.silence_auto_exp…

    fxn authored
    Rationale: As discussed with José and Jon, this convenience
    shortcut is not clearly justified and it could let the user
    thing the disabled EXPLAINs are related to the model instance
    rather than being globally disabled.
Commits on Dec 2, 2011
  1. @fxn
  2. @fxn
Commits on Dec 1, 2011
  1. @dhh

    Revert "Added ActiveRecord::Base#last_modified to work with the new f…

    dhh authored
    …resh_when/stale? conditional get methods from Action Pack"
    Needless indirection with no added value.
    This reverts commit 535853e.
  2. @dhh

    Added ActiveRecord::Base#last_modified to work with the new fresh_whe…

    dhh authored
    …n/stale? conditional get methods from Action Pack
Commits on Nov 30, 2011
  1. @bogdan
Commits on Nov 29, 2011
  1. @tenderlove

    Automatic closure of connections in threads is deprecated. For example

    tenderlove authored
    the following code is deprecated: { Post.find(1) }.join
    It should be changed to close the database connection at the end of
    the thread: {
    Only people who spawn threads in their application code need to worry
    about this change.
  2. @jonleighton
  3. @jonleighton
  4. @jonleighton
  5. @jonleighton
  6. @jonleighton
  7. @jonleighton

    Merge pull request #3636 from joshsusser/master

    jonleighton authored
    association methods are now generated in modules
Commits on Nov 27, 2011
  1. @joshsusser
Commits on Nov 19, 2011
  1. @jonleighton

    Perf fix

    jonleighton authored
    If we're deleting all records in an association, don't add a IN(..)
    clause to the query.
    Fixes #3672.
  2. @jonleighton
  3. @jonleighton

    Verify that #3690 has been closed by previous changes to the mysql

    jonleighton authored
    These tests fail on the v3.1.2 tag.
    Closes #3690.
Commits on Nov 14, 2011
  1. @jonleighton
Commits on Nov 6, 2011
  1. @fxn

    implements AR::Relation#explain

    fxn authored
    This is a first implementation, EXPLAIN is highly
    dependent on the database and I have made some
    On one hand, the method allows you to run the most
    common EXPLAIN and that's it. If you want EXPLAIN
    ANALYZE in PostgreSQL you need to do it by hand.
    On the other hand, I've tried to construct a string
    as close as possible to the ones built by the
    respective shells. The rationale is that IMO the
    user should feel at home with the output and
    recognize it at first sight. Per database.
    I don't know whether this implementation is going
    to work well. Let's see whether people like it.
Commits on Nov 5, 2011
  1. @jonleighton

    Merge pull request #3525 from kennyj/fix_3440-1

    jonleighton authored
    Fixed an issue id false option is ignored on mysql/mysql2 (fix #3440)
  2. @kennyj
  3. @jonleighton
Commits on Nov 4, 2011
  1. @vjebelev
  2. @jonleighton

    Convert CHANGELOGs to Markdown format.

    jonleighton authored
     * Markdown reads well as plain text, but can also be formatted.
     * It will make it easier for people to read on the web as Github
       formats the Markdown nicely.
     * It will encourage a level of consistency when people are writing
       CHANGELOG entries.
    The script used to perform the conversion is at
Something went wrong with that request. Please try again.