diff options
| author | yuuji.yaginuma <yuuji.yaginuma@gmail.com> | 2019-02-23 13:03:53 +0900 |
|---|---|---|
| committer | yuuji.yaginuma <yuuji.yaginuma@gmail.com> | 2019-02-23 13:35:27 +0900 |
| commit | 619ae03f60c00e0870cd391b3252091b005fe948 (patch) | |
| tree | 810ddd35b2fdef97a1f615a80cc26f26c089e83e /activesupport/test/encrypted_configuration_test.rb | |
| parent | a796de1bd644b54e2c27577319c262af0de56e8f (diff) | |
| download | rails-619ae03f60c00e0870cd391b3252091b005fe948.tar.gz rails-619ae03f60c00e0870cd391b3252091b005fe948.tar.bz2 rails-619ae03f60c00e0870cd391b3252091b005fe948.zip | |
Make `test_select_with_subquery_in_from_uses_original_table_name` work with old SQLite3
It seems that the reason why the `test_select_with_subquery_in_from_uses_original_table_name`
does not pass is that the return value of `sqlite3_column_name()` is
wrong due to subquery flattening.
This seems to have been fixed with SQLite 3.20.0(https://sqlite.org/changes.html#version_3_20_0).
But CI uses the old version(maybe 3.11.0), I added `DISTINCT` to avoid
optimization by subquery flattening.
Ref: https://sqlite.org/optoverview.html#flattening
Diffstat (limited to 'activesupport/test/encrypted_configuration_test.rb')
0 files changed, 0 insertions, 0 deletions