rails.git - Mirror of official rails repo with custom fixes.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Optimizer hints should be applied on Top level query as much as possible	Ryuta Kamizono	2019-04-04	1	-0/+8
\| \| \| \| \|	I've experienced this issue in our app, some hints only works on Top level query (e.g. `MAX_EXECUTION_TIME`).
*	Add test case to prevent possible SQL injection	Ryuta Kamizono	2019-03-18	1	-0/+10
\|
*	Add test case for unscoping `:optimizer_hints`	Ryuta Kamizono	2019-03-18	1	-0/+6
\|
*	Support Optimizer Hints	Ryuta Kamizono	2019-03-16	1	-0/+24
	We as Arm Treasure Data are using Optimizer Hints with a monkey patch (https://gist.github.com/kamipo/4c8539f0ce4acf85075cf5a6b0d9712e), especially in order to use `MAX_EXECUTION_TIME` (refer #31129). Example: ```ruby class Job < ApplicationRecord default_scope { optimizer_hints("MAX_EXECUTION_TIME(50000) NO_INDEX_MERGE(jobs)") } end ``` Optimizer Hints is supported not only for MySQL but also for most databases (PostgreSQL on RDS, Oracle, SQL Server, etc), it is really helpful to turn heavy queries for large scale applications.