aboutsummaryrefslogtreecommitdiffstats
path: root/activerecord/test/cases
Commit message (Collapse)AuthorAgeFilesLines
* Has many through - It is not necessary to manually merge in the conditions ↵Jon Leighton2011-01-301-1/+11
| | | | hash for the through record, because the creation is done directly on the through association, which will already handle setting the conditions.
* AssociationCollection#clear can basically just use #delete_all, except it ↵Jon Leighton2011-01-301-3/+6
| | | | should return self.
* AssociationCollection#to_ary should definitely dup the target! Also changed ↵Jon Leighton2011-01-301-0/+7
| | | | #replace which was previously incorrect, but the test passed due to the fact that to_a was not duping.
* DRY up first/last and hence make last benefit from the bugfix in firstJon Leighton2011-01-301-0/+6
|
* We shouldn't be using scoped.scoping { ... } to build associated records, as ↵Jon Leighton2011-01-302-1/+32
| | | | this can affect validations/callbacks/etc inside the record itself [#6252 state:resolved]
* Fixing incorrectly writtent testcaseAlexey Nayden2011-01-281-2/+2
|
* test_first_and_array_index_zero_methods_return_the_same_value_when_nested_at ↵Alexey Nayden2011-01-281-0/+9
| | | | tributes_are_set_to_update_existing_record added
* fixing bug where 1.8 hangs while running pg testsAaron Patterson2011-01-181-1/+1
|
* fixing unused variable warningsAaron Patterson2011-01-171-3/+3
|
* Removed support for accessing attributes on a has_and_belongs_to_many join ↵Jon Leighton2011-01-162-92/+0
| | | | table. This has been documented as deprecated behaviour since April 2006. Please use has_many :through instead. A deprecation warning will be added to the 3-0-stable branch for the 3.0.4 release.
* belongs_to records should be initialized within the association scopeJon Leighton2011-01-161-0/+21
|
* Add create_association! for belongs_toJon Leighton2011-01-161-0/+17
|
* transactional fixtures must be set to false for this testAaron Patterson2011-01-141-1/+1
|
* preheat the table cache in arelAaron Patterson2011-01-141-0/+1
|
* Add missing requireSantiago Pastorino2011-01-141-0/+1
|
* include_in_memory? should check against @target list in case of new records. ↵Aaron Patterson2011-01-121-0/+7
| | | | [#6257 state:resolved]
* adding a test for no method errorAaron Patterson2011-01-111-0/+52
|
* use underlying _read_attribute method rather than causing NoMethodErrorsAaron Patterson2011-01-111-1/+1
|
* Support for create_association! for has_one associationsJon Leighton2011-01-111-0/+18
|
* Get rid of set_association_target and association_loaded? as the parts of ↵Jon Leighton2011-01-111-1/+1
| | | | the code that need that can now just use association_proxy(:name).loaded?/target=
* DRY up the code which instantiates the association proxyJon Leighton2011-01-111-13/+0
|
* Raise ActiveRecord::RecordNotSaved if an AssociationCollection fails to be ↵Jon Leighton2011-01-111-0/+13
| | | | replaced
* When assigning a has_one, if anything fails, the assignment should be rolled ↵Jon Leighton2011-01-111-2/+5
| | | | back entirely
* In a number of places in the tests, we only need to turn off transactional ↵Jon Leighton2011-01-119-43/+51
| | | | fixtures when the DB does not support savepoints. This speeds the test run up by about 8-9% on my computer, when running rake test_sqlite3_mem :)
* When assigning a has_one, if the new record fails to save, raise an errorJon Leighton2011-01-112-16/+16
|
* When assigning a has_one, if the existing record fails to be removed from ↵Jon Leighton2011-01-111-0/+12
| | | | the association, raise an error
* Enable the sqlite3 in-memory test connection to workJon Leighton2011-01-114-8/+15
|
* has_one should always remove the old record (properly), even if not saving ↵Jon Leighton2011-01-111-10/+25
| | | | the new record, so we don't get the database into a pickle
* Fix polymorphic belongs_to associationproxy raising errors when loading target.Ernie Miller2011-01-111-0/+9
|
* Always return decimal average of integer fieldsRaimonds Simanovskis2011-01-101-0/+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.
* use SQLite3::VERSION rather than the deprecated classAaron Patterson2011-01-101-1/+1
|
* Add test for e0e3adfJeremy Kemper2011-01-071-0/+6
|
* Don't not remove double negativesJon Leighton2011-01-071-1/+1
|
* Construct an actual ActiveRecord::Relation object for the association scope, ↵Jon Leighton2011-01-073-11/+4
| | | | 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/+7
|
* just use a hash for doing association cachingAaron Patterson2011-01-073-4/+3
|
* adding an `encode_with` method for Psych dump/load methodsAaron Patterson2011-01-051-0/+7
|
* make sure new objects can round tripAaron Patterson2011-01-051-0/+6
|
* make sure that Psych can roundtrip an AR objectAaron Patterson2011-01-051-0/+13
|
* fixing merge errorsAaron Patterson2011-01-042-78/+0
|
* Remove undocumented feature from has_one where you could pass false as the ↵Jon Leighton2011-01-032-36/+7
| | | | | | | | | | | | 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-031-0/+4
| | | | ActiveRecord::Base.primary_key does.
* Implement deprecated version of AssociationReflection#primary_key_name, ↵Jon Leighton2011-01-031-0/+12
| | | | 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-031-0/+9
| | | | 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.
* Make Relation#create_with always merge rather than overwrite, not just when ↵Jon Leighton2011-01-031-0/+10
| | | | 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).
* Let AssociationCollection#find use #scoped to do its finding. Note that I am ↵Jon Leighton2011-01-033-14/+12
| | | | removing test_polymorphic_has_many_going_through_join_model_with_disabled_include, since this specifies different behaviour for an association than for a regular scope. It seems reasonable to expect scopes and association proxies to behave in roughly the same way rather than having subtle differences.
* Fix test_any in relations_test.rb, which was failing when relations_test.rb ↵Jon Leighton2011-01-031-0/+8
| | | | is run on its own (it passes when the entire suite is run). This is a hacky fix for a problem I didn't quite get to the bottom of, so I'd welcome a better solution...
* Allow assignment on has_one :through where the owner is a new record [#5137 ↵Jon Leighton2011-01-035-23/+60
| | | | | | | | | | state:resolved] This required changing the code to keep the association proxy for a belongs_to around, despite its target being nil. Which in turn required various changes to the way that stale target checking is handled, in order to support various edge cases (loaded target is nil then foreign key added, foreign key is changed and then changed back, etc). A side effect is that the code is nicer and more succinct. Note that I am removing test_no_unexpected_aliasing since that is basically checking that the proxy for a belongs_to *does* change, which is the exact opposite of the intention of this commit. Also adding various tests for various edge cases and related things. Phew, long commit message!
* Have a proper AssociationReflection#foreign_type method rather than using ↵Jon Leighton2011-01-031-0/+6
| | | | options[:foreign_type]
* Some basic tests for the :foreign_type option on belongs_to, which was ↵Jon Leighton2011-01-032-1/+31
| | | | previously completely untested.
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-11 15:50:34 +0000