- 08 1月, 2011 9 次提交
-
-
由 Jon Leighton 提交于
-
由 Jon Leighton 提交于
Construct an actual ActiveRecord::Relation object for the association scope, rather than a hash which is passed to apply_finder_options. This allows more flexibility in how the scope is created, for example because scope.where(a, b) and scope.where(a).where(b) mean different things.
-
由 Jon Leighton 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
- 07 1月, 2011 3 次提交
-
-
由 Aaron Patterson 提交于
-
由 Nick Sutterer 提交于
-
由 Nick Sutterer 提交于
-
- 06 1月, 2011 12 次提交
-
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
- 05 1月, 2011 13 次提交
-
-
由 Hemant Kumar 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
* rsim/require_deprecation: require ActiveSupport deprecatation file before using deprecate method in database_statements
-
由 Aaron Patterson 提交于
* rsim/habtm_select_fix: Explicitly select * from has_and_belongs_to_many association tables, simplify exists? query
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Pratik Naik 提交于
-
由 Prem Sichanugrist 提交于
-
由 Prem Sichanugrist 提交于
-
由 Prem Sichanugrist 提交于
-
- 04 1月, 2011 3 次提交
-
-
由 Raimonds Simanovskis 提交于
Previous version (after commit 3103296a) was generating wrong SQL for Oracle when calling exists? method on HABTM association.
-
由 Raimonds Simanovskis 提交于
otherwise when using external ActiveRecord adapters (e.g. Oracle) database_statements might be loaded before active_support/core_ext/module/deprecation which results in NoMethodError (commit 60cf65de added "deprecate" call to database_statements.rb)
-
由 Jon Leighton 提交于
Remove undocumented feature from has_one where you could pass false as the second parameter to build_assoc or create_assoc, and the existing associated object would be untouched (the foreign key would not be nullified, and it would not be deleted). If you want behaviour similar to this you can do the following things: * Use :dependent => :nullify (or don't specify :dependent) if you want to prevent the existing associated object from being deleted * Use has_many if you actually want multiple associated objects * Explicitly set the foreign key if, for some reason, you really need to have multiple objects associated with the same has_one. E.g. previous = obj.assoc obj.create_assoc previous.update_attributes(:obj_id => obj.id)
-