diff options
| author | Keenan Brock <keenan@thebrocks.net> | 2016-04-20 11:23:56 -0400 |
|---|---|---|
| committer | Keenan Brock <keenan@thebrocks.net> | 2016-04-28 17:48:41 -0400 |
| commit | dffbba1e2aed01748cfc79327946175ad51f6b4f (patch) | |
| tree | 801974e5d7c2a14b1a7855209ee9c743c93857f0 /Gemfile | |
| parent | ef5c46d2ee8dc8da20f54dbedc9805f71791d75c (diff) | |
| download | rails-dffbba1e2aed01748cfc79327946175ad51f6b4f.tar.gz rails-dffbba1e2aed01748cfc79327946175ad51f6b4f.tar.bz2 rails-dffbba1e2aed01748cfc79327946175ad51f6b4f.zip | |
schema_load triggers 2nd schema_load (via locking)
Currently, loading the schema (schema_load)
accesses the locking column (locking_column)
which defaults the value (reset_locking_column)
which invalidates the schema (reload_schema_from_cache)
which forces another schema load.
Good news:
The second schema_load does accesses locking_column,
but locking_column is set, so it does not reset_locking_column
and it does not trigger an infinite loop.
The solution is not invalidate the cache while default locking_column
Diffstat (limited to 'Gemfile')
0 files changed, 0 insertions, 0 deletions