7 Commits

Author	SHA1	Message	Date
Xavier Noria	29d564add9	Merge pull request #6197 from blakesmith/connection_adapters_without_explain_support ... Don't run explain on slow queries for database adapters that don't support it	2013-01-22 19:54:01 -02:00
kennyj	d95f3d3f73	Fix build. It seems that the Mocha's behavior were changed.	2012-04-24 15:00:36 -05:00
Xavier Noria	24834606c2	disable automatic explain if there is no logger [closes #4671]	2012-01-26 02:51:18 -08:00
Xavier Noria	cfeac38e2b	implements a much faster auto EXPLAIN, closes #3843 [José Valim & Xavier Noria] ... This commit vastly reduces the impact of auto explain logging when enabled, while keeping a negligible cost when disabled. The first implementation was based on the idea of subscribing to "sql.active_record" when needed, and unsubscribing once done. This is the idea behind AR::Relation#explain. Subscribe, collect, unsubscribe. But with the current implementation of notifications unsubscribing is costly, because it wipes an internal cache and that puts a penalty on the next event. So we are switching to an approach where a long-running subscriber is listening. Instead of collecting the queries with a closure in a dedicated subscriber, now we setup a thread local. If the feature is disabled by setting the threshold to nil, the subscriber will call a method that does nothing. That's totally cheap.	2011-12-04 11:52:12 -08:00
Xavier Noria	de24ed9f2d	removes the convenience instance version of AR::Base.silence_auto_explain ... Rationale: As discussed with José and Jon, this convenience shortcut is not clearly justified and it could let the user thing the disabled EXPLAINs are related to the model instance rather than being globally disabled.	2011-12-03 14:26:34 +01:00
Xavier Noria	0be5adaedf	implements AR::Base(.|#)silence_auto_explain	2011-12-02 11:16:26 -08:00
Xavier Noria	0306f82e0c	implements automatic EXPLAIN logging for slow queries	2011-12-02 04:35:43 -08:00