Jean Boussier 091dc78f94 Forward sql.active_record notifications back into the calling thread ... It is not uncommon for `sql.active_record` subscribers to rely on thread local or fiber local state. For instance the `buffered-logger` gem buffer the logs in a thread variable. With the introduction of async queries, the `sql.active_record` events can now be produced from a background thread and that break some expectations. This makes it hard for subscriber to map the event to the request or job that scheduled it. That is why I believe we should instead store the event and publish it back on the calling thread when the results are accessed.		2021-03-03 10:33:37 +01:00
..
evented_notification_test.rb	allow running each test with pure ruby path/to/test.rb	2019-12-18 08:49:19 -06:00
instrumenter_test.rb	Forward sql.active_record notifications back into the calling thread	2021-03-03 10:33:37 +01:00