aboutsummaryrefslogtreecommitdiffstats
path: root/activerecord/test/cases
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | | | Extract the short-hand methods into `ColumnMethods`Ryuta Kamizono2015-02-231-0/+8
| | | | | |
| * | | | | Extract `primary_key` method into `ColumnMethods`Ryuta Kamizono2015-02-221-0/+7
| | | | | |
* | | | | | Allow `:limit` option for MySQL bigint primary key supportRyuta Kamizono2015-02-241-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Example: create_table :foos, id: :primary_key, limit: 8 do |t| end # or create_table :foos, id: false do |t| t.column :id, limit: 8 end
* | | | | | Require `belongs_to` by default.Josef Šimánek2015-02-211-0/+50
|/ / / / / | | | | | | | | | | | | | | | Deprecate `required` option in favor of `optional` for belongs_to.
* | | | | Error message testing fixFranky W2015-02-203-5/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The testing of error messages have been implemented wrongly a few times. This is an attempt to fix it. For example, some of these test should have failed with the new code. The reason they are not failling with the new string is the fact they were not being tested beforehand.
* | | | | Merge branch 'rm-take' into 4-1-stableRafael Mendonça França2015-02-201-1/+29
| | | | |
* | | | | Do not test, document or use a private API methodRafael Mendonça França2015-02-202-23/+0
| | | | | | | | | | | | | | | | | | | | These methods are nodoc so we should not document them.
* | | | | Merge pull request #16989 from Empact/reload-cache-clearRafael Mendonça França2015-02-201-2/+2
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | Isolate access to @associations_cache and @aggregations_cache to the Associations and Aggregations modules, respectively.
| * | | | | Isolate access to @associations_cache and @aggregations cache to the ↵Ben Woosley2014-09-283-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Associations and Aggregations modules, respectively. This includes replacing the `association_cache` accessor with a more limited `association_cached?` accessor and making `clear_association_cache` and `clear_aggregation_cache` private.
* | | | | | Merge pull request #17139 from mfazekas/fix_becomes_changed_attributesRafael Mendonça França2015-02-201-0/+6
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | Always reset changed attributes in becomes
| * | | | | | Always reset changed attributes in becomesMiklos Fazekas2015-02-041-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When ```becomes``` changes @attributes it should also change @changed_attributes. Otherwise we'll experience a kind of split head situation where attributes are coming from ```self```, but changed_attributes is coming from ```klass.new```. This affects the inheritance_colmn as it's changed by new for example. Fixes #16881
* | | | | | | Add schema dumping tests for datetime and time precisionRyuta Kamizono2015-02-203-8/+34
| | | | | | |
* | | | | | | Format the time string according to the precision of the time columnRyuta Kamizono2015-02-201-0/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | It is also necessary to format a time column like a datetime column.
* | | | | | | Allow `:precision` option for time type columnsRyuta Kamizono2015-02-202-1/+66
| | | | | | |
* | | | | | | Merge pull request #18916 from kamipo/handle_array_option_in_type_to_sqlRafael Mendonça França2015-02-191-0/+7
|\ \ \ \ \ \ \ | | | | | | | | | | | | | | | | Handle array option in `type_to_sql`
| * | | | | | | Should handle array option for `:cast_as`Ryuta Kamizono2015-02-191-0/+7
| | | | | | | |
* | | | | | | | Merge pull request #18979 from ↵Rafael Mendonça França2015-02-191-1/+1
|\ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | kamipo/extract_precision_from_datetime_and_time_columns Extract precision from datetime and time columns
| * | | | | | | | Extract precision from datetime and time columnsRyuta Kamizono2015-02-191-1/+1
| |/ / / / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The cause by which the test suite for the mysql adapter broke in 1502cae (reverted 89ba5bb) is because the precision was not extracted. The rounding problem in mysql adapter has not been fixed, but `mysql_56` helper tested only mysql2 adapter, its behavior was not apparent.
* | | | | | | | Copy edit the suppressor documentationRafael Mendonça França2015-02-191-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | [ci skip]
* | | | | | | | Add `ActiveRecord::Base.suppress`Michael Ryan2015-02-181-0/+22
|/ / / / / / /
* | | | | | / Add `time` option to `#touch`Hyonjee Joo2015-02-181-0/+21
| |_|_|_|_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes #18905. `#touch` now takes time as an option. Setting the option saves the record with the updated_at/on attributes set to the current time or the time specified. Updated tests and documentation accordingly.
* | | | | | Prefer `drop_table if_exists: true` over raw SQLRyuta Kamizono2015-02-1820-24/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Lowercase raw SQL has been replaced by 07b659c already. This commit replaces everything else of raw SQL.
* | | | | | prefer `drop_table if_exists: true` over raw SQL.Yves Senn2015-02-1812-12/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | /cc @yahonda This makes it easier for third party adapters to run our tests, even if that database does not support IF EXISTS.
* | | | | | Rm `Type#type_cast`Sean Griffin2015-02-172-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This helper no longer makes sense as a separate method. Instead I'll just have `deserialize` call `cast` by default. This led to a random infinite loop in the `JSON` pg type, when it called `super` from `deserialize`. Not really a great way to fix that other than not calling super, or continuing to have the separate method, which makes the public API differ from what we say it is.
* | | | | | `type_cast_from_user` -> `cast`Sean Griffin2015-02-1712-90/+90
| | | | | |
* | | | | | `type_cast_for_database` -> `serialize`Sean Griffin2015-02-1714-46/+46
| | | | | |
* | | | | | `Type#type_cast_from_database` -> `Type#deserialize`Sean Griffin2015-02-1716-44/+44
| | | | | |
* | | | | | Fix test failures on Mysql 5.5Sean Griffin2015-02-171-1/+1
| | | | | |
* | | | | | Update code which depended on methods added by 1502caefSean Griffin2015-02-171-1/+1
| | | | | |
* | | | | | Revert "Allow `:precision` option for time type columns"Sean Griffin2015-02-171-65/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 1502caefd30b137fd1a0865be34c5bbf85ba64c1. The test suite for the mysql adapter broke when this commit was used with MySQL 5.6. Conflicts: activerecord/CHANGELOG.md
* | | | | | Deprecated passing of `start` value to `find_in_batches` and `find_each` in ↵Vipul A M2015-02-171-7/+28
| | | | | | | | | | | | | | | | | | | | | | | | favour of `begin_at` value.
* | | | | | Merge pull request #18662 from estum/foreign-key-existsYves Senn2015-02-161-0/+21
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | Add `foreign_key_exists?` method.
| * | | | | | Add `foreign_key_exists?` method.Anton2015-01-241-0/+21
| | | | | | |
* | | | | | | Add a global type registry, used to lookup and register typesSean Griffin2015-02-152-0/+172
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As per previous discussions, we want to give users the ability to reference their own types with symbols, instead of having to pass the object manually. This adds the class that will be used to do so. ActiveRecord::Type.register(:money, MyMoneyType)
* | | | | | | Mention `where.not` in the exampleGodfrey Chan2015-02-141-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ...so it doesn't look like you *have* to use SQL strings for that case (not anymore!). Would like to replace the SQL string example with something that you cannot do with the "normal" query API, but I could not come up with a short, realistic example. Suggestions welcome!
* | | | | | | Fixed a bug where NULLs are casted into the first enum valueGodfrey Chan2015-02-131-3/+8
| | | | | | |
* | | | | | | Partially revert ae33aeaGodfrey Chan2015-02-131-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Using enum names in SQL strings doesn't actually work, the test was wrong (fixed in 3dfd1ba).
* | | | | | | Break up these testsGodfrey Chan2015-02-131-4/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Make sure we have coverage for both the find/build cases
* | | | | | | oops, 'format' is not a real enumGodfrey Chan2015-02-131-8/+8
| | | | | | |
* | | | | | | Enums should be referred to by symbolsGodfrey Chan2015-02-131-1/+14
| |_|_|_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | Also updated the documentation about the new ability to query them normally, and added test to make sure they work!
* | | | | | Do not overwrite secret token value when already present.Wojciech Wnętrzak2015-02-121-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ``` user = User.create(token: "custom-secure-token") user.token # => "custom-secure-token" ```
* | | | | | Merge pull request #18915 from kamipo/extract_date_time_precision_testRafael Mendonça França2015-02-124-271/+102
|\ \ \ \ \ \ | | | | | | | | | | | | | | Extract `DateTimePrecisionTest`
| * | | | | | Extract `DateTimePrecisionTest`Ryuta Kamizono2015-02-134-271/+102
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The datetime precision tests for any adapters is duplicated.
* | | | | | | Optimize none? and one? relation query methods to use LIMIT and COUNT.Eugene Gilburg2015-02-122-0/+110
|/ / / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use SQL COUNT and LIMIT 1 queries for none? and one? methods if no block or limit is given, instead of loading the entire collection to memory. The any? and many? methods already follow this behavior. [Eugene Gilburg & Rafael Mendonça França]
* | | | | | Merge pull request #18886 from kamipo/allow_precision_option_for_time_columnRafael Mendonça França2015-02-121-0/+65
|\ \ \ \ \ \ | | | | | | | | | | | | | | Allow `:precision` option for time type columns
| * | | | | | Allow `:precision` option for time type columnsRyuta Kamizono2015-02-121-0/+65
| | | | | | |
* | | | | | | get rid of transaction warning when running PG tests.Yves Senn2015-02-121-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This finally removes the warning "WARNING: there is no transaction in progress" when running Active Record tests using PostgreSQL.
* | | | | | | pg tests, be clear about the missing type that causes a test skip.Yves Senn2015-02-122-15/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Also removed some cruft in the `setup` and `teardown` methods.
* | | | | | | tests, remove unused requires.Yves Senn2015-02-122-2/+0
|/ / / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | "active_support/testing/stream" is already required in `test_case.rb`. Furthermore the test "test/cases/migration_test.rb" could no longer be executed directly.
* | | | | | Refactor enum to be defined in terms of the attributes APISean Griffin2015-02-111-1/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In addition to cleaning up the implementation, this allows type casting behavior to be applied consistently everywhere. (#where for example). A good example of this was the previous need for handling value to key conversion in the setter, because the number had to be passed to `where` directly. This is no longer required, since we can just pass the string along to where. (It's left around for backwards compat) Fixes #18387
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-19 20:27:18 +0000