aboutsummaryrefslogtreecommitdiffstats
path: root/activerecord/lib/active_record
Commit message (Collapse)AuthorAgeFilesLines
* has_one should always remove the old record (properly), even if not saving ↵Jon Leighton2011-01-111-1/+1
| | | | the new record, so we don't get the database into a pickle
* Return value is irrelevant here as the RHS of the assignment is always ↵Jon Leighton2011-01-111-1/+0
| | | | returned by methods ending in '='
* Remove incorrect documentation about build_assoc on has_one. This is proven, ↵Jon Leighton2011-01-111-2/+1
| | | | for example, by test_successful_build_association in has_one_associations_test.rb
* For a singular association, it should be build_association, rather than ↵Jon Leighton2011-01-111-1/+1
| | | | association.build (as association may be nil)
* Correctly indent the bullet points under 'One-to-one associations', so that ↵Jon Leighton2011-01-111-10/+10
| | | | the lines are not broken in the generated rdoc html
* avoid splatting arrays by using concatAaron Patterson2011-01-111-3/+3
|
* Fix polymorphic belongs_to associationproxy raising errors when loading target.Ernie Miller2011-01-111-0/+5
|
* only use one array when collecting split up queriesAaron Patterson2011-01-101-1/+1
|
* Always return decimal average of integer fieldsRaimonds Simanovskis2011-01-101-9/+5
| | | | In previous version if database adapter (e.g. SQLite and Oracle) returned non-String calculated values then type_cast_using_column converted decimal average value of intefer field to integer value. Now operation parameter is always checked to decide which conversion of calculated value should be done.
* Adding postgresql template option when executing db:test:clone_structureKatrina Owen2011-01-091-1/+1
| | | | | | | | | | Specify the template to use in config/database.yml, e.g. test: adapter: postgresql template: template_postgis If no template is specified, postgresql defaults to template1
* remove unused string substitutionAaron Patterson2011-01-081-6/+1
|
* use select_all because not all database adapters support bind valuesAaron Patterson2011-01-081-1/+1
|
* join the cult of cargo. reduce the number of NoMethodErrors in the systemAaron Patterson2011-01-071-1/+1
|
* stop creating intermediate AR objects, just construct AR objects from a list ↵Aaron Patterson2011-01-071-1/+2
| | | | of hashes
* no need for to_symAaron Patterson2011-01-071-1/+1
|
* String#insert() mutates the string, so no need for lasgnAaron Patterson2011-01-071-1/+1
|
* fewer funcalls to the cached attributes variableAaron Patterson2011-01-071-1/+1
|
* Refactor HasOneAssociation#replaceJon Leighton2011-01-071-26/+22
|
* Don't not remove double negativesJon Leighton2011-01-071-4/+4
|
* Clean up create, create! and build in HasOneAssociationJon Leighton2011-01-071-14/+8
|
* merge_with_conditions is not necessary because the conditions will already ↵Jon Leighton2011-01-071-9/+0
| | | | be in the scope_for_create hash in the scope
* Not really worth having the HasAssociation module for just a single methodJon Leighton2011-01-075-21/+9
|
* Construct an actual ActiveRecord::Relation object for the association scope, ↵Jon Leighton2011-01-078-113/+72
| | | | 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.
* Use encode_with for marshallingJon Leighton2011-01-071-0/+20
|
* send() will raise an ArgumentError, so we should leverage rubyAaron Patterson2011-01-071-16/+6
|
* no need for parensAaron Patterson2011-01-071-1/+1
|
* use a hash for caching aggregations rather than ivarsAaron Patterson2011-01-072-14/+9
|
* method is never called with argumentsAaron Patterson2011-01-071-4/+2
|
* only rescue from Mysql::Error exceptions [#6236 state:resolved]Aaron Patterson2011-01-071-4/+9
|
* just use a hash for doing association cachingAaron Patterson2011-01-073-11/+14
|
* no need for selfAaron Patterson2011-01-061-1/+1
|
* adding an `encode_with` method for Psych dump/load methodsAaron Patterson2011-01-051-0/+16
|
* AR internals expect a normal hash, otherwise there are serialization ↵Aaron Patterson2011-01-051-1/+1
| | | | incompatibilities
* no need to specify selfAaron Patterson2011-01-051-1/+1
|
* no need to send a symbol to send()Aaron Patterson2011-01-051-1/+1
|
* avoid creating so many Arel::Table objectsAaron Patterson2011-01-051-6/+9
|
* use attr_reader and alias methods to access instance variablesAaron Patterson2011-01-051-8/+4
|
* we have a method for this, so let's use itAaron Patterson2011-01-051-2/+2
|
* use arel ast construction rather than generating stringsAaron Patterson2011-01-051-1/+7
|
* use arel to construct AST rather than generate stringsAaron Patterson2011-01-051-2/+3
|
* Merge remote branch 'rsim/require_deprecation'Aaron Patterson2011-01-041-0/+2
|\ | | | | | | | | * rsim/require_deprecation: require ActiveSupport deprecatation file before using deprecate method in database_statements
| * require ActiveSupport deprecatation file before using deprecate method in ↵Raimonds Simanovskis2011-01-041-0/+2
| | | | | | | | | | database_statements 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 60cf65def805995bcca184c40b44bb01d86a48aa added "deprecate" call to database_statements.rb)
* | Explicitly select * from has_and_belongs_to_many association tables, ↵Raimonds Simanovskis2011-01-042-2/+3
|/ | | | | simplify exists? query Previous version (after commit 3103296a61709e808aa89c3d37cf22bcdbc5a675) was generating wrong SQL for Oracle when calling exists? method on HABTM association.
* Remove undocumented feature from has_one where you could pass false as the ↵Jon Leighton2011-01-032-28/+11
| | | | | | | | | | | | 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)
* ActiveRecord::Relation#primary_key should return a string, just like ↵Jon Leighton2011-01-036-28/+21
| | | | ActiveRecord::Base.primary_key does.
* Implement deprecated version of AssociationReflection#primary_key_name, ↵Jon Leighton2011-01-031-0/+6
| | | | which has been renamed to #foreign_key. Also bumping the deprecation_horizon in Active Support to 3.1.
* When preloading a belongs_to, the target should still be set (to nil) if ↵Jon Leighton2011-01-033-12/+16
| | | | there is no foreign key present. And the loaded flag should be set on the association proxy. This then allows us to remove the foreign_key_present? check from BelongsToAssociation#find_target. Also added a test for the same thing on polymorphic associations.
* Create the association scope directly rather than going through with_scopeJon Leighton2011-01-037-31/+32
|
* Make Relation#create_with always merge rather than overwrite, not just when ↵Jon Leighton2011-01-032-4/+2
| | | | merging two relations. If you wish to overwrite, you can do relation.create_with(nil), or for a specific attribute, relation.create_with(:attr => nil).
* Use the association directly in other places tooJon Leighton2011-01-033-20/+13
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 04:34:40 +0000