- 19 11月, 2012 1 次提交
-
-
由 Jarek Radosz 提交于
-
- 17 11月, 2012 1 次提交
-
-
由 Carlos Antonio da Silva 提交于
-
- 12 11月, 2012 2 次提交
- 10 11月, 2012 1 次提交
-
-
由 Bogdan Gusiev 提交于
-
- 05 11月, 2012 1 次提交
-
-
由 Yves Senn 提交于
-
- 03 11月, 2012 2 次提交
-
-
由 Rafael Mendonça França 提交于
This was there due historical reasons since 7dc45818 to give the user the possibility to create unique indexes passing "UNIQUE" as the third argument
-
由 Rafael Mendonça França 提交于
Closes #8104
-
- 31 10月, 2012 3 次提交
-
-
由 Alexis Bernard 提交于
-
由 Nikita Afanasenko 提交于
Public method `attributes_before_type_cast` used to return internal AR structure (ActiveRecord::AttributeMethods::Serialization::Attribute), patch fixes this. Now behaves like `read_attribute_before_type_cast` and returns unserialised values.
-
由 kennyj 提交于
-
- 29 10月, 2012 4 次提交
-
-
由 Juanjo Bazán 提交于
-
由 Henrik N 提交于
Didn't work before because it updated the model-in-memory first, so the DB query couldn't find the record.
-
由 Yves Senn 提交于
-
由 Francesco Rodriguez 提交于
This fixes the following behaviour: class Person < ActiveRecord::Base belongs_to :company end # Before: person = Person.select('id').first person[:name] # => nil person.name # => ActiveModel::MissingAttributeError: missing_attribute: name person[:company_id] # => nil person.company # => nil # After: person = Person.select('id').first person[:name] # => ActiveModel::MissingAttributeError: missing_attribute: name person.name # => ActiveModel::MissingAttributeError: missing_attribute: name person[:company_id] # => ActiveModel::MissingAttributeError: missing_attribute: company_id person.company # => ActiveModel::MissingAttributeError: missing_attribute: company_id Fixes #5433.
-
- 28 10月, 2012 1 次提交
-
-
由 Victor Costan 提交于
-
- 27 10月, 2012 1 次提交
-
-
由 Shawn Veader 提交于
The RFC indicates that username and passwords may be encoded. http://tools.ietf.org/html/rfc2396#section-3.2.2 Found this trying to use the mysql://username:password@host:port/db and having special characters in the password which needed to be URI encoded.
-
- 26 10月, 2012 1 次提交
-
-
由 Jon Leighton 提交于
In the end I think the pain of implementing this seamlessly was not worth the gain provided. The intention was that it would allow plain ruby objects that might not live in your main application to be subclassed and have persistence mixed in. But I've decided that the benefit of doing that is not worth the amount of complexity that the implementation introduced.
-
- 24 10月, 2012 1 次提交
-
-
由 Uģis Ozols 提交于
-
- 21 10月, 2012 1 次提交
-
-
由 Jeremy Kemper 提交于
This reverts commit 83846838.
-
- 20 10月, 2012 1 次提交
-
-
由 Jon Leighton 提交于
I think it's going to be too much pain to try to transition the :active_record load hook from executing against Base to executing against Model. For example, after Model is included in Base, and modules included in Model will no longer get added to the ancestors of Base. So plugins which wish to be compatible with both Model and Base should use the :active_record_model load hook which executes *before* Base gets loaded. In general, ActiveRecord::Model is an advanced feature at the moment and probably most people will continue to inherit from ActiveRecord::Base for the time being.
-
- 19 10月, 2012 3 次提交
-
-
由 Jon Leighton 提交于
This reflects the fact that it now impact inserts as well as updates.
-
由 Jon Leighton 提交于
-
由 Jon Leighton 提交于
This is similar to #first_or_create, but slightly different and a nicer API. See the CHANGELOG/docs in the commit. Fixes #7853
-
- 17 10月, 2012 1 次提交
-
-
由 Scott Willson 提交于
Would incorrectly add duplicated errors when the association was blank. Bug introduced in 1fab518c.
-
- 16 10月, 2012 3 次提交
-
-
由 Christian Seiler 提交于
Call super to nullify the reference to the original errors object in the dup'ed object (call ActiveModel::Validations#initialize_dup). Closes #7291
-
由 Carlos Antonio da Silva 提交于
-
由 Tim Macfarlane 提交于
-
- 14 10月, 2012 1 次提交
-
-
由 Arturo Pie 提交于
-
- 12 10月, 2012 1 次提交
-
-
由 Tima Maslyuchenko 提交于
-
- 08 10月, 2012 1 次提交
-
-
由 Alexey Muranov 提交于
-
- 05 10月, 2012 1 次提交
-
-
由 Yves Senn 提交于
-
- 04 10月, 2012 2 次提交
-
-
由 Rafael Mendonça França 提交于
-
由 Francesco Rodriguez 提交于
Patches `CollectionAssociation#count` to return 0 without querying if the parent record is new. Consider the following code: class Account has_many :dossiers end class Dossier belongs_to :account end a = Account.new a.dossiers.build # before patch a.dossiers.count # SELECT COUNT(*) FROM "dossiers" WHERE "dossiers"."account_id" IS NULL # => 0 # after a.dosiers.count # fires without sql query # => 0 Fixes #1856.
-
- 02 10月, 2012 1 次提交
-
-
由 lulalala 提交于
The counter column name in the intermediate model need to be access via the through reflection.
-
- 29 9月, 2012 3 次提交
-
-
由 Rafael Mendonça França 提交于
-
由 Jon Leighton 提交于
When inserting new records, only the fields which have been changed from the defaults will actually be included in the INSERT statement. The other fields will be populated by the database. This is more efficient, and also means that it will be safe to remove database columns without getting subsequent errors in running app processes (so long as the code in those processes doesn't contain any references to the removed column).
-
由 Sebastian Martinez 提交于
-
- 24 9月, 2012 1 次提交
-
-
由 John Foley 提交于
-
- 22 9月, 2012 1 次提交
-
-
由 Santiago Pastorino 提交于
This reverts commit 761bc751. This commit wasn't fixing any issue just using the same table for different models with different primary keys.
-