aboutsummaryrefslogtreecommitdiffstats
path: root/activerecord/test
Commit message (Collapse)AuthorAgeFilesLines
...
* | | | | Don't error when `dup`ing a record with no PKSean Griffin2014-07-021-0/+12
| | | | |
* | | | | do not hold on to a stale connection object. fixes #15998Aaron Patterson2014-07-011-2/+5
| | | | |
* | | | | Add regression tests for keys on nested associationseileencodes2014-07-011-0/+32
|/ / / / | | | | | | | | | | | | | | | | | | | | This adds the regressions tests from issue #15893 to master. It's checking that both strings and symbols are accepted as keys for nested associations.
* | | | Use the type object for sending JSON to the databaseSean Griffin2014-06-291-1/+1
| | | |
* | | | Always pass a column with a type object to quoteSean Griffin2014-06-282-13/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The only case where we got a column that was not `nil`, but did not respond to `cast_type` was when type casting the default value during schema creation. We can look up the cast type, and add that object to the column definition. Will allow us to consistently rely on the type objects for type casting in all directions.
* | | | [Postgresql tests] remove duplicate helperAbdelkader Boudih2014-06-281-12/+3
| | | |
* | | | MySQL doesn't work with foreign keysPhilippe Creux2014-06-271-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | This was previously fixed in e84799d but broken in 3f596f8. This commit reintroduced the conditional that prevents the foreign keys from being added to MySQL databases.
* | | | Fix test with add_foreign_key DSL in 9d21ef9Philippe Creux2014-06-271-1/+1
| | | |
* | | | Merge pull request #15934 from seuros/renameRafael Mendonça França2014-06-271-0/+10
|\ \ \ \ | | | | | | | | | | | | | | | rename primary key sequence only if it exists
| * | | | rename sequence only if it existsAbdelkader Boudih2014-06-271-0/+10
| | | | |
* | | | | Do not change the global state of the test suiteRafael Mendonça França2014-06-272-18/+2
| | | | |
* | | | | Improve tests to use add_foreign_key DSLRafael Mendonça França2014-06-271-18/+11
| | | | |
* | | | | MySQL doesn't works with foreign keyRafael Mendonça França2014-06-271-3/+2
|/ / / /
* | | | Merge pull request #12450 from iantropov/masterRafael Mendonça França2014-06-271-0/+36
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix bug, when ':dependent => :destroy' violates foreign key constraints Conflicts: activerecord/CHANGELOG.md activerecord/lib/active_record/associations/builder/association.rb activerecord/lib/active_record/associations/builder/has_one.rb
| * | | | Fix bug, when ':dependent => :destroy' option violates foreign key ↵Ivan Antropov2013-10-261-0/+36
| | | | | | | | | | | | | | | | | | | | constraints, issue #12380
* | | | | Merge pull request #15788 from sgrif/sg-mutable-stringsRafael Mendonça França2014-06-273-12/+39
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | Detect in-place modifications on Strings
| * | | | | Detect in-place modifications on StringsSean Griffin2014-06-173-12/+39
| | | | | |
* | | | | | Merge pull request #8639 from bogdan/valid-with-bangRafael Mendonça França2014-06-271-0/+14
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | Add AR::Base#valid! method
| * | | | | | Add AR::Base#validate! methodBogdan Gusiev2014-06-231-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Acts same as valid? but raises AR::RecordInvalid exception if validation fails
* | | | | | | fk: use random digest namesYves Senn2014-06-264-20/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The name of the foreign key is not relevant from a users perspective. Using random names resolves the urge to rename the foreign key when the respective table or column is renamed.
* | | | | | | fk: raise for invalid :on_update / :on_delete valuesYves Senn2014-06-261-0/+10
| | | | | | |
* | | | | | | fk: `add/remove_foreign_key` are noop for adapters that don't support fkYves Senn2014-06-261-0/+24
| | | | | | |
* | | | | | | fk: dump foreign keys at the bottom to make sure tables exist.Yves Senn2014-06-261-0/+7
| | | | | | |
* | | | | | | fk: raise when identifiers are longer than `allowed_index_name_length`.Yves Senn2014-06-261-0/+9
| | | | | | |
* | | | | | | fk: support for on_updateYves Senn2014-06-261-3/+13
| | | | | | |
* | | | | | | fk: rename `dependent` to `on_delete`Yves Senn2014-06-261-13/+13
| | | | | | |
* | | | | | | fk: infere column name from table names.Yves Senn2014-06-262-2/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This allows to create and remove foreign keys without specifying a column.
* | | | | | | fk: make `add_foreign_key` reversible.Yves Senn2014-06-262-0/+39
| | | | | | |
* | | | | | | fk: support dependent option (:delete, :nullify and :restrict).Yves Senn2014-06-261-0/+42
| | | | | | |
* | | | | | | fk: dump foreign keys to schema.rbYves Senn2014-06-262-1/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | respect `table_name_prefix` and `table_name_suffix`.
* | | | | | | fk: `:primary_key` option for non-standard pk's.Yves Senn2014-06-262-2/+22
| | | | | | |
* | | | | | | fk: generalize using `AlterTable` and `SchemaCreation`.Yves Senn2014-06-261-2/+4
| | | | | | |
* | | | | | | fk: `foreign_keys`, `add_foreign_key` and `remove_foreign_key` for MySQLYves Senn2014-06-261-0/+5
| | | | | | |
* | | | | | | fk: add `foreign_keys` for PostgreSQL adapter.Yves Senn2014-06-261-7/+27
| | | | | | |
* | | | | | | fk: `add_foreign_key` and `remove_foreign_key` for PostgreSQL adapter.Yves Senn2014-06-261-0/+49
| | | | | | |
* | | | | | | Merge pull request #15924 from sgrif/sg-write-unknown-columnRafael Mendonça França2014-06-263-2/+20
|\ \ \ \ \ \ \ | | | | | | | | | | | | | | | | Move writing unknown column exception to null attribute
| * | | | | | | Move writing unknown column exception to null attributeSean Griffin2014-06-263-2/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Making this change revealed several subtle bugs related to models with no primary key, and anonymous classes. These have been fixed as well, with regression tests added.
* | | | | | | | Merge pull request #15916 from sgrif/sg-test-update-allRafael Mendonça França2014-06-264-30/+28
|\ \ \ \ \ \ \ \ | |/ / / / / / / |/| | | | | | | Consolidate testing of update_all type casting
| * | | | | | | Consolidate testing of update_all type castingSean Griffin2014-06-264-30/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We have several test cases on "tricky" types that are essentially testing that `update_all` goes through the same type casting behavior as a normal assignment + save. We recently had another case to add this test for another type in https://github.com/rails/rails/pull/12742. Rather than testing this separately for every type which is "tricky" when round tripping, let's instead have a fairly exhaustive test that ensures we're getting the correct values at every step for `update_all`. Given the structure of the code now, we can be confident that if the type is correct, and `update_all` is type casting correctly, we're going to get the right behavior for all types.
* | | | | | | | Deprecate automatic counter caches on has_many :throughSean Griffin2014-06-2612-35/+59
|/ / / / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Reliant on https://github.com/rails/rails/pull/15747 but pulled to a separate PR to reduce noise. `has_many :through` associations have the undocumented behavior of automatically detecting counter caches. However, the way in which it does so is inconsistent with counter caches everywhere else, and doesn't actually work consistently. As with normal `has_many` associations, the user should specify the counter cache on the `belongs_to`, if they'd like it updated.
* | | | | | | `Attribute` should know about its nameSean Griffin2014-06-262-12/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This allows using polymorphism for the uninitialized attributes raising an exception behavior.
* | | | | | | Encapsulate the creation of `Attribute` objectsSean Griffin2014-06-262-1/+61
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This will make it less painful to add additional properties, which should persist across writes, such as `name`. Conflicts: activerecord/lib/active_record/attribute_set.rb
* | | | | | | Merge pull request #15868 from sgrif/sg-uninitialized-attributesRafael Mendonça França2014-06-261-0/+56
|\ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Move behavior of `read_attribute` to `AttributeSet` Conflicts: activerecord/lib/active_record/attribute_set.rb activerecord/test/cases/attribute_set_test.rb
| * | | | | | | Move behavior of `read_attribute` to `AttributeSet`Sean Griffin2014-06-251-0/+56
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Moved `Builder` to its own file, as it started looking very weird once I added private methods to the `AttributeSet` class and the `Builder` class started to grow. Would like to refactor `fetch_value` to change to ```ruby self[name].value(&block) ``` But that requires the attributes to know about their name, which they currently do not.
* | | | | | | | Merge pull request #15847 from sgrif/sg-encapsulate-result-typesRafael Mendonça França2014-06-261-4/+40
|\ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | Encapsulate knowledge of type objects on `ActiveRecord::Result`
| * | | | | | | | Encapsulate knowledge of type objects on `ActiveRecord::Result`Sean Griffin2014-06-221-4/+40
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Attempting to reduce the number of places that care about the details of how type casting occurs. We remove the type casting of the primary key in `JoinDependecy`, rather than encapsulating it. It was originally added for consistency with https://github.com/rails/rails/commit/40898c8c19fa04442fc5f8fb5daf3a8bdb9a1e03#diff-06059df8d3dee3101718fb2c01151ad0R211, but that conditional was later removed in https://github.com/rails/rails/commit/d7ddaa530fd1b94e22d745cbaf2e8a5a34ee9734. What is important is that the same row twice will have the same value for the primary key, which it will.
* | | | | | | | | Merge pull request #15846 from sgrif/sg-attributes-before-type-castRafael Mendonça França2014-06-261-0/+7
|\ \ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Move `attributes_before_type_cast` to `AttributeSet` Conflicts: activerecord/lib/active_record/attribute_set.rb activerecord/test/cases/attribute_set_test.rb
| * | | | | | | | | Move `attributes_before_type_cast` to `AttributeSet`Sean Griffin2014-06-211-0/+7
| | | | | | | | | |
* | | | | | | | | | `preload` preserves readonly flag on associations. #15853Yves Senn2014-06-251-0/+29
| |_|_|_|_|_|_|_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a partial fix for #15853. It only works when a `preload` is issued and not an `eager_load`. I've added a skipped failing test-case to keep in mind that we need to deal with `eager_load`.
* | | | | | | | | Always assume strings with non-numeric characters change numeric typesSean Griffin2014-06-241-0/+18
| |_|/ / / / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We previously only did this if the old value was zero, to make sure numericality validations run and failed if the user gave 'wibble' as the value, which would be type cast to 0. However, numericality validations will fail if there are any non-numeric characters in the string, so 5 -> '5wibble' should also be marked as changed.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-06 11:24:15 +0000