diff options
| author | Sean Griffin <sean@seantheprogrammer.com> | 2016-03-31 13:04:14 -0600 |
|---|---|---|
| committer | Sean Griffin <sean@seantheprogrammer.com> | 2016-03-31 13:04:14 -0600 |
| commit | 04ac5655be91f49cd4dfe2838df96213502fb274 (patch) | |
| tree | 29df317be73e7e6f8c889c318809eddaff70b9f9 /activerecord/lib/active_record/core.rb | |
| parent | 42cbd4ae1e5ccb654e1e522756188b28e4ab8347 (diff) | |
| download | rails-04ac5655be91f49cd4dfe2838df96213502fb274.tar.gz rails-04ac5655be91f49cd4dfe2838df96213502fb274.tar.bz2 rails-04ac5655be91f49cd4dfe2838df96213502fb274.zip | |
Ensure associations still work when the table name contains a dot
This issue occured because associations now call `where` directly, and a
dot in the key name for `where` means nested tables. For this fix, we
now pass the table name as a symbol, and do not attempt to expand
symbols containing a dot.
This is a temporary fix. I do not think we should support table names
containing a dot, as it has a special meaning in most backends, as well
as most APIs that involve table names. This commit does not include a
test, as I am going to deprecate table names containing dots in the
following commit.
Fixes #24367
Diffstat (limited to 'activerecord/lib/active_record/core.rb')
0 files changed, 0 insertions, 0 deletions