aboutsummaryrefslogtreecommitdiffstats
path: root/activerecord/test
Commit message (Collapse)AuthorAgeFilesLines
...
* | Merge pull request #28733 from kamipo/dont_fallback_to_utf8mb3_after_mysql_8.0.0Rafael França2017-04-191-2/+2
|\ \ | | | | | | Don't fallback to utf8mb3 after MySQL 8.0.0
| * | Don't fallback to utf8mb3 after MySQL 8.0.0Ryuta Kamizono2017-04-171-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `internal_string_options_for_primary_key` is used for creating internal tables in newly apps. But it is no longer needed after MySQL 8.0.0. MySQL 5.7 has introduced `innodb_default_row_format` (default `DYNAMIC`) and has deprecated `innodb_large_prefix` and `innodb_file_format`. The purpose of the deprecated options was for compatibility with earlier versions of InnoDB. https://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_large_prefix > innodb_large_prefix is deprecated and will be removed in a future release. innodb_large_prefix was introduced in MySQL 5.5 to disable large index key prefixes for compatibility with earlier versions of InnoDB that do not support large index key prefixes. https://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_file_format > The innodb_file_format option is deprecated and will be removed in a future release. The purpose of the innodb_file_format option was to allow users to downgrade to the built-in version of InnoDB in MySQL 5.1. Now that MySQL 5.1 has reached the end of its product lifecycle, downgrade support provided by this option is no longer necessary. The deprecated options has removed in MySQL 8.0.0. It is no longer needed to take care newly created internal tables as a legacy format after MySQL 8.0.0. Fixes #28730.
* | | Merge pull request #28776 from kamipo/respect_limit_for_cache_keyRafael França2017-04-191-2/+28
|\ \ \ | | | | | | | | `cache_key` respects the limit in a relation even if a relation is not loaded
| * | | `cache_key` respects the limit in a relation even if a relation is not loadedRyuta Kamizono2017-04-171-2/+28
| |/ / | | | | | | | | | | | | | | | `cache_key` includes the size of a relation. But if a relation is not loadded, the size is not respected even if a relation has a limit. It should be respected for consistency.
* | | Merge pull request #28161 from bogdanvlviv/add_test_attributesRafael França2017-04-181-0/+11
|\ \ \ | |/ / |/| | Add test for method `#attributes`
| * | Add test for method `#attributes`bogdanvlviv2017-02-251-0/+11
| | | | | | | | | | | | | | | | | | ActiveRecord::AttributeMethods#attributes Extracted from https://github.com/rails/rails/pull/28159
* | | Support Descending Indexes for MySQLRyuta Kamizono2017-04-161-1/+5
| | | | | | | | | | | | | | | | | | | | | MySQL 8.0.1 and higher supports descending indexes: `DESC` in an index definition is no longer ignored. See https://dev.mysql.com/doc/refman/8.0/en/descending-indexes.html.
* | | Move around AR::Dirty and fix _attribute methodAaron Patterson2017-04-141-0/+22
| | | | | | | | | | | | | | | | | | We already have a _read_attribute method that can get the value we need from the model. Lets define that method in AM::Dirty and use the existing one from AR::Dirty rather than introducing a new method.
* | | Merge pull request #28661 from ↵Aaron Patterson2017-04-141-0/+19
|\ \ \ | | | | | | | | | | | | | | | | bogdanvlviv/fix-dirty-attributes-if-override-attr_accessor Fix inconsistency with changed attributes when overriding AR attribute reader
| * | | Fix inconsistency with changed attributes when overriding AR attribute readerbogdanvlviv2017-04-121-0/+19
| | | |
* | | | Add a test case for #20802Ryuta Kamizono2017-04-132-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | The issue #20802 has been fixed in cc0b566. Closes #20802.
* | | | :scissors:Ryuta Kamizono2017-04-132-2/+0
| | | | | | | | | | | | | | | | [ci skip]
* | | | Use a query that's compatible with PostgreSQL 9.2Matthew Draper2017-04-124-8/+16
|/ / / | | | | | | | | | | | | | | | Also, explicitly apply the order: generate_subscripts is unlikely to start returning values out of order, but we should still be clear about what we want.
* | | Merge pull request #28721 from koic/oracle_does_not_support_limit_clauseRafael França2017-04-111-1/+1
|\ \ \ | | | | | | | | Fix an AR test of relations_test when using Oracle
| * | | Fix an AR test of relations_test when using OracleKoichi ITO2017-04-111-1/+1
| | | |
* | | | exclude ORDER BY clause for exists? (#28699)Boris Slobodin2017-04-101-0/+5
|/ / /
* | | More exercise `exists?` testsRyuta Kamizono2017-04-081-5/+18
| | |
* | | Passing in no arguments to the dynamic fixture accessor method returns all ↵Kevin McPhillips2017-04-071-0/+18
| | | | | | | | | | | | fixtures, not an empty array.
* | | Remove duplicated "test" prefixRyuta Kamizono2017-04-073-4/+4
| |/ |/|
* | Ignore AR tests of index comment when using OracleKoichi ITO2017-04-051-5/+9
| |
* | Merge pull request #28029 from koic/empty_insert_statement_value_not_supportedMatthew Draper2017-04-042-0/+4
|\ \ | | | | | | Raise NotImplementedError when using empty_insert_statement_value with Oracle
| * | Raise NotImplementedError when using empty_insert_statement_value with OracleKoichi ITO2017-02-172-0/+4
| | | | | | | | | | | | Refer: https://github.com/rsim/oracle-enhanced/pull/1180
* | | Fix a failed AR test when running with OracleAdapterKoichi ITO2017-03-311-0/+2
| | |
* | | Merge pull request #28592 from ↵Rafael França2017-03-291-0/+6
|\ \ \ | | | | | | | | | | | | | | | | htanata/ar_relation_inspect_should_not_load_all_records Load only needed records on ActiveRecord::Relation#inspect
| * | | Load only needed records on ActiveRecord::Relation#inspectHendy Tanata2017-03-281-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Instead of loading all records and returning only a subset of those, just load the records as needed. Fixes #25537.
* | | | Merge pull request #28478 from kamipo/fix_primary_keys_across_multiple_schemasAndrew White2017-03-291-1/+2
|\ \ \ \ | | | | | | | | | | Fix `primary_keys` across multiple schemas
| * | | | Fix `primary_keys` across multiple schemasRyuta Kamizono2017-03-201-1/+2
| | | | | | | | | | | | | | | | | | | | Fixes #28470.
* | | | | Merge pull request #28052 from kamipo/make_internal_methods_to_privateRafael França2017-03-281-1/+1
|\ \ \ \ \ | |_|/ / / |/| | | | Make internal methods to private
| * | | | Make internal methods to privateRyuta Kamizono2017-03-271-1/+1
| | | | |
* | | | | Merge pull request #27636 from ↵Rafael França2017-03-2722-94/+133
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | mtsmfm/disable-referential-integrity-without-superuser-privilege-take-2 Use `SET CONSTRAINTS` for `disable_referential_integrity` without superuser privileges (take 2)
| * | | | | Load :author_addressesYasuo Honda2017-03-261-1/+1
| | | | | |
| * | | | | Use `SET CONSTRAINTS` for `disable_referential_integrity` without superuser ↵Fumiaki MATSUSHIMA2017-03-2621-93/+132
| |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | privileges (take 2) Re-create https://github.com/rails/rails/pull/21233 eeac6151a5 was reverted (127509c071b4) because it breaks tests. ---------------- ref: 72c1557254 - We must use `authors` fixture with `author_addresses` because of its foreign key constraint. - Tests require PostgreSQL >= 9.4.2 because it had a bug about `ALTER CONSTRAINTS` and fixed in 9.4.2.
* / / / / Fixes #28359Philippe Guay2017-03-261-0/+8
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add stronger assertions to rake migration tasks to make sure the user is providing a numeric VERSION An empty string was getting converted to version = 0. This would in turn pass the presence check. Address linting warning Add test for rake task and refactor code to meet expectations In particular passing VERSION=0 should not raise an error. Addressed Comments for PR #28485. Trimmed empty lines + change of wording for error message Adjust test for change of wording in error message Change condition to follow rails idioms
* | | | Merge pull request #28526 from kamipo/fix_log_subscriber_to_allow_legacy_bindsRafael França2017-03-221-58/+63
|\ \ \ \ | | | | | | | | | | Fix `LogSubscriber` to allow legacy `binds`
| * | | | Fix `LogSubscriber` to allow legacy `binds`Ryuta Kamizono2017-03-231-58/+63
| | | | | | | | | | | | | | | | | | | | Follow up of #27939.
* | | | | Merge pull request #28531 from yahonda/suppress_pg_warningMatthew Draper2017-03-231-0/+1
|\ \ \ \ \ | | | | | | | | | | | | Suppress `WARNING: nonstandard use of \\ in a string literal` warning
| * | | | | Suppress `WARNING: nonstandard use of \\ in a string literal` warningYasuo Honda2017-03-221-0/+1
| |/ / / / | | | | | | | | | | | | | | | by setting `escape_string_warning = off`
* / / / / [PostgreSQL]: Replace deprecated PG constants.Lars Kanis2017-03-221-4/+4
|/ / / / | | | | | | | | | | | | | | | | The old top level classes PGconn, PGresult and PGError were deprecated since pg-0.13.0: https://github.com/ged/ruby-pg/blob/master/History.rdoc#v0130-2012-02-09-michael-granger-gedfaeriemudorg
* | | | Fix where_clause#except with specific where valueJohn Hawthorn2017-03-201-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes a regression introduced in 22ca710f20c3c656811df006cbf1f4dbc359f7a6 where Relation#unscope with a specific where value (vs unscoping the entire where clause) could result in the wrong binds being left on the query. This was caused by an index variable not being incremented properly.
* | | | Merge pull request #28474 from kamipo/fix_extension_with_darty_targetKasper Timm Hansen2017-03-202-0/+9
|\ \ \ \ | | | | | | | | | | Fix extension method with dirty target in has_many associations
| * | | | Fix extension method with dirty target in has_many associationsRyuta Kamizono2017-03-202-0/+9
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | Extension methods should not delegate to `scope` to respect dirty target on `CollectionProxy`. Fixes #28419.
* | | | Merge pull request #28473 from kamipo/delegate_uniq_to_recordsRafael França2017-03-203-19/+19
|\ \ \ \ | | | | | | | | | | Delegate `uniq` to `records`
| * | | | Use `load` rather than `collect` for force loadingRyuta Kamizono2017-03-193-19/+19
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | Since b644964b `ActiveRecord::Relation` includes `Enumerable` so delegating `collect`, `all?`, and `include?` are also unneeded. `collect` without block returns `Enumerable` without preloading by that. We should use `load` rather than `collect` for force loading.
* | | | Merge pull request #27939 from kamipo/fix_select_all_with_legacy_bindsRafael França2017-03-201-0/+9
|\ \ \ \ | |/ / / |/| | | Fix `select_all` with legacy `binds`
| * | | Fix `select_all` with legacy `binds`Ryuta Kamizono2017-02-121-0/+9
| | | | | | | | | | | | | | | | Fixes #27923.
* | | | Merge pull request #28191 from eugeneius/string_assoc_orderRafael França2017-03-171-1/+24
|\ \ \ \ | | | | | | | | | | Allow order to be given expressions as hash keys
| * | | | Allow order to be given expressions as hash keysEugene Kenny2017-02-271-1/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When `order` is given a hash, the keys are currently assumed to be attribute names and are quoted as such in the query, which makes it impossible to pass an expression instead: Post.order("LENGTH(title)" => :asc).last # SELECT `posts`.* FROM `posts` ORDER BY `posts`.`LENGTH(title)` DESC LIMIT 1 If the key is an `Arel::Nodes::SqlLiteral`, we now use it directly in the query. This provides a way to build a relation with a complex order clause that can still be reversed with `reverse_order` or `last`.
* | | | | Merge pull request #28154 from aripollak/remove-comments-from-structure-sqlRafael Mendonça França2017-03-171-3/+16
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | Drop comments from structure.sql in postgresql
| * | | | | Only remove comments before the first statementAri Pollak2017-02-241-3/+3
| | | | | |
| * | | | | Drop comments from structure.sql in postgresqlAri Pollak2017-02-241-3/+16
| | | | | | | | | | | | | | | | | | | | | | | | Fixes #28153.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-07 23:20:32 +0000