Skip to content
This repository

Dec 23, 2013

  1. Richard Schneeman

    Tell how to Create a Database in Error Message

    Currently if you attempt to use a database that does not exist  you get an error:
    PG::ConnectionBad FATAL:  database "db_error" does not exist
    The solution is easy, create and migrate your database however new developers may not know these commands by memory. Instead of requiring the developer to search for a solution, tell them how to fix the problem in the error message:
    ActiveRecord::NoDatabase: FATAL:  database "db_error" does not exist
    Run `$ bin/rake db:create db:migrate` to create your database
    Active Record should not know about `rake db:migrate` so this additional information needs to come from the railtie. Potential alternative implementation suggestions are welcome.
    authored November 11, 2013

Dec 12, 2013

  1. Akshay Vishnoi

    Spelling and Grammar checks

    authored December 12, 2013

Jun 07, 2013

  1. Jon Leighton

    Merge pull request #10561 from Empact/nix-throwresult

    Rather than raising ThrowResult when construct_limited_ids_conditions comes up empty, set the relation to NullRelation and rely on its results.
    authored June 07, 2013

May 16, 2013

  1. Bogdan Gusiev

    Add more data to AR::UnknownAttributeError

    begin"hello" => "world")
    rescue ActiveRecord::UnknownAttributeError => e
      e.record # => #<Topic ... >
      e.attribute # => "hello"
    authored May 13, 2013 tenderlove committed May 16, 2013

May 10, 2013

  1. Ben Woosley

    Rather than raising ThrowResult when construct_limited_ids_conditions…

    … comes up empty, set the relation to NullRelation and rely on its results.
    This will help avoid errors like 2fcafee, because in most cases NullRelation will do the right thing. Minor bonus is avoiding the use of exceptions for flow control.
    authored May 10, 2013

Apr 29, 2013

  1. Jeremy Kemper

    StatementInvalid takes WrappedDatabaseException's place

    authored April 23, 2013

Nov 10, 2012

  1. Avner Cohen

    1.9 Syntax related changes

    authored November 10, 2012

Nov 02, 2012

  1. Vijay Dev

    copy edits [ci skip]

    authored November 03, 2012

Oct 26, 2012

  1. Francesco Rodríguez

    update AR::ImmutableRelation documentation [ci skip]

    authored October 26, 2012

Sep 21, 2012

  1. Jon Leighton

    Support for specifying transaction isolation level

    If your database supports setting the isolation level for a transaction,
    you can set it like so:
      Post.transaction(isolation: :serializable) do
        # ...
    Valid isolation levels are:
    * `:read_uncommitted`
    * `:read_committed`
    * `:repeatable_read`
    * `:serializable`
    You should consult the documentation for your database to understand the
    semantics of these different levels:
    An `ActiveRecord::TransactionIsolationError` will be raised if:
    * The adapter does not support setting the isolation level
    * You are joining an existing open transaction
    * You are creating a nested (savepoint) transaction
    The mysql, mysql2 and postgresql adapters support setting the
    transaction isolation level. However, support is disabled for mysql
    versions below 5, because they are affected by a bug
    ( which means the isolation level
    gets persisted outside the transaction.
    authored September 21, 2012

Jun 27, 2012

  1. Maurício Linhares

    Fixes #6825, adds tests covering cases and error possibilities, also …

    …changes SQLite3 driver to correctly generate a time column instead of datetime
    authored June 27, 2012

Jun 22, 2012

  1. Jon Leighton

    disallow mutating a relation once loaded

    authored June 22, 2012

Jun 06, 2012

  1. Marc-André Lafortune

    + ActiveRecord::Base#destroy!

    authored June 05, 2012

Oct 14, 2011

  1. Christian Bäuerlein

    Consider attempted action in exception message of ActiveRecord::Stale…

    authored October 14, 2011
  2. Christian Bäuerlein

    Includes stale record in StaleObjectError

    authored October 14, 2011

Oct 05, 2011

  1. Jon Leighton

    Raise an exception on unknown primary key inside AssociationReflection.

    An association between two models cannot be made if a relevant key is
    unknown, so fail fast rather than generating invalid SQL. Fixes #3207.
    authored October 05, 2011
  2. Jon Leighton

    Revert "Raise error on unknown primary key."

    This reverts commit ee2be43.
    authored October 05, 2011
  3. Jon Leighton

    Raise error on unknown primary key.

    If we don't have a primary key when we ask for it, it's better to fail
    fast. Fixes GH #2307.
    authored October 05, 2011

Jul 07, 2011

  1. Akira Matsuda

    :conditions => where

    authored July 08, 2011
  2. Akira Matsuda

    find(:all) => all

    authored July 08, 2011

Aug 14, 2010

  1. Santiago Pastorino

    Deletes trailing whitespaces (over text files only find * -type f -ex…

    …ec sed 's/[ \t]*$//' -i {} \;)
    authored August 14, 2010

Aug 02, 2010

  1. Neeraj Singh

    ensuring that description does not exceed 100 columns

    authored August 02, 2010

Jun 15, 2010

  1. Rizwan Reza

    Adds title.

    authored June 15, 2010

Mar 07, 2010

  1. Yehuda Katz

    Make many parts of Rails lazy. In order to facilitate this,

    add lazy_load_hooks.rb, which allows us to declare code that
    should be run at some later time. For instance, this allows
    us to defer requiring ActiveRecord::Base at boot time purely
    to apply configuration. Instead, we register a hook that should
    apply configuration once ActiveRecord::Base is loaded.
    With these changes, brings down total boot time of a
    new app to 300ms in production and 400ms in dev.
    TODO: rename base_hook
    authored March 07, 2010
Something went wrong with that request. Please try again.