- 28 6月, 2017 5 次提交
-
-
由 Ryuta Kamizono 提交于
```ruby car = Car.create!(name: "Tofaş") # Before car.bulb_ids # => SELECT "bulbs".ID FROM "bulbs" WHERE "bulbs"."name" = $1 AND "bulbs"."car_id" = $2 [["name", "defaulty"], ["car_id", 3]] # After car.bulb_ids # => SELECT "bulbs"."ID" FROM "bulbs" WHERE "bulbs"."name" = $1 AND "bulbs"."car_id" = $2 [["name", "defaulty"], ["car_id", 3]] ```
-
由 Ryuta Kamizono 提交于
And use `assert_same` instead of `assert_equal` and tiny fix assert message s/#reload/#reset/. Follow up of #29511.
-
由 Tobias Kraze 提交于
If a record was built on a HasManyThroughAssociation, then removed, and then the record was saved, the removed record would be created anyways.
-
由 Grey Baker 提交于
-
由 Ryuta Kamizono 提交于
`test_exceptional_middleware_clears_and_disables_cache_on_error` in postgresql adapter sometime fails recently. Show the query cache keys to investigte the cause. https://travis-ci.org/rails/rails/jobs/246467252#L490-L493
-
- 27 6月, 2017 3 次提交
-
-
由 Ryuta Kamizono 提交于
-
由 Ryuta Kamizono 提交于
-
由 Ryuta Kamizono 提交于
Simply we can skip instantiating `NullPreloader` if `assoc.klass` is nil.
-
- 26 6月, 2017 2 次提交
-
-
由 Ryuta Kamizono 提交于
-
由 Ryuta Kamizono 提交于
-
- 25 6月, 2017 2 次提交
-
-
由 Ryuta Kamizono 提交于
Covering #27994 in tests. Closes #27994.
-
由 Ray Zane 提交于
The AliasTracker#aliased_table_for needs the type caster for the joined association, not the join root
-
- 24 6月, 2017 2 次提交
-
-
由 Ryuta Kamizono 提交于
-
由 Ryuta Kamizono 提交于
-
- 22 6月, 2017 4 次提交
-
-
由 yuuji.yaginuma 提交于
This fixes the following warnings: ``` activerecord/test/cases/relation_test.rb:231: warning: assigned but unused variable - authors_with_commented_posts ```
-
由 John Hawthorn 提交于
-
由 Edouard CHIN 提交于
-
由 Edouard CHIN 提交于
- On Mysql, some command line options that affect option-file handling such as `--no-defaults` have to be passed before any other options - Modified rails to pass them right after the `mysql` command - Ref https://dev.mysql.com/doc/refman/5.7/en/option-file-options.html and https://bugs.mysql.com/bug.php?id=83386 - Ref #27437
-
- 21 6月, 2017 6 次提交
-
-
由 Kir Shatrov 提交于
Scalar values like arrays and hashes can't be inserted directly into table. Previously, the way to determine if the value is scalar was to try quoting it. If `quote` raised with an error than the value has to be converted to YAML. This flow is not very obvious. Ideally we could have a `quotable?` method in the connection, but I think that we can avoid begin/rescue block by simply checking if the value is Array or Hash. https://github.com/rails/rails/commit/aa31d21f5f4fc4d679e74a60f9df9706da7de373
-
由 Maxime Lapointe 提交于
Doing `Author.joins(:posts).merge(Post.joins(:comments))` does this `SELECT ... INNER JOIN posts ON... LEFT OUTER JOIN comments ON...` instead of doing `SELECT ... INNER JOIN posts ON... INNER JOIN comments ON...`. This behavior is unexpected and makes little sense as, basically, doing `Post.joins(:comments)` means I want posts that have comments. Turning it to a LEFT JOIN means I want posts and join the comments data, if any. We can see this problem directly in the existing tests. The test_relation_merging_with_merged_joins_as_symbols only does joins from posts to comments to ratings while the ratings fixture isn't loaded, but the count is non-zero.
-
由 John Hawthorn 提交于
The `@offsets` cache is used by FinderMethods to cache records found by find_nth. This cache is cleared in AR::Relation#reset, but not in CollectionProxy#reset or CollectionProxy#reload. Because of this, since #29098, calling #first/#find_nth/etc after calling #reload or #reset on an association could return a stale record. This is an issue both when the full association target is loaded and when the item is loaded in #find_nth. This commit solves the problem by clearing the `@offsets` cache in CollectionProxy#reset and CollectionProxy#reload.
-
由 bogdanvlviv 提交于
`ActiveRecord::Persistence#touch` does not work well when optimistic locking enabled and `locking_column`, without default value, is null in the database.
-
由 bogdanvlviv 提交于
Fix destroying existing object does not work well when optimistic locking enabled and `locking column` is null in the database. Follow 22a822e5, #28914
-
由 Kir Shatrov 提交于
Improves the performance from O(n) to O(1). Previously it would require 50 queries to insert 50 fixtures. Now it takes only one query. Disabled on sqlite which doesn't support multiple inserts.
-
- 20 6月, 2017 1 次提交
-
-
由 Kir Shatrov 提交于
-
- 18 6月, 2017 3 次提交
-
-
由 Ryuta Kamizono 提交于
Because constructing `scope` is a little expensive.
-
由 Ryuta Kamizono 提交于
This debug print was added in 87f5e5e2 for finding the regression caused by d314646c and the regression has already been fixed in 969339bd.
-
由 Ryuta Kamizono 提交于
A part for JSON was splitted from #28416 as #29273 and #29273 has already been merged. Closes #28754. Closes #27588. [Ryuta Kamizono & Bradley Priest]
-
- 17 6月, 2017 1 次提交
-
-
由 Kir Shatrov 提交于
Unlike with other databses, MySQL doesn't let you remove the column if there's a FK on this column. For better developer experience we want to remove the FK together with the column.
-
- 16 6月, 2017 1 次提交
-
-
由 Ryuta Kamizono 提交于
`id` column in `subscribers` was added as a primary key for ignorable in INSERT. But it caused `NotNullViolation` for oracle-enhanced adapter. https://github.com/rsim/oracle-enhanced/issues/1357 I changed the column to nullable to address the issue.
-
- 15 6月, 2017 9 次提交
-
-
由 Eugene Kenny 提交于
The `raw_write_attribute` method is used to update a record's attributes to reflect the new state of the database in `update_columns`. The hash provided to `update_columns` is turned into an UPDATE query directly, which means passing an `id` key results in an update to the `id` column, even if the model uses a different attribute as its primary key. When updating the record, we don't want to apply the `id` column change to the primary key attribute, since that's not what happened in the query. Without the code to handle this case, `write_attribute_with_type_cast` no longer contains any logic shared between `raw_write_attribute` and `write_attribute`, so we can inline the code into those two methods.
-
由 Ryuta Kamizono 提交于
Fixes #29460.
-
由 Dan Sherson 提交于
-
由 Vipul A M 提交于
-
由 Ryuta Kamizono 提交于
-
由 Ryuta Kamizono 提交于
If a connection adapter overrides `select_*` methods, query caching will doesn't work. This patch changes `select_value` to `select_one` in `Relation#exists?` to ensure query caching. Fixes #29449.
-
由 Ryuta Kamizono 提交于
`object.id` is correctly restored since #29378 has merged. Closes #28274, Closes #28395. [Ryuta Kamizono & Eugene Kenny]
-
由 Ryuta Kamizono 提交于
`sync_with_transaction_state` in `to_key` is unneeded because `id` also does.
-
由 Eugene Kenny 提交于
Running `bin/test` from the activerecord directory produces this error: test/cases/adapters/postgresql/uuid_test.rb:43:in `<class:PostgresqlUUIDTest>': undefined method `supports_pgcrypto_uuid?' for #<ActiveRecord::ConnectionAdapters::SQLite3Adapter:0x007fc405e72a68> (NoMethodError) The test only actually runs on the PostgreSQL adapter; we can avoid triggering the error on other adapters with this `respond_to?` guard.
-
- 14 6月, 2017 1 次提交
-
-
由 bogdanvlviv 提交于
-