Override MySQL's check for accidental large queries
Bug 1070046: MySQL has an optional server config option, "MAX_JOIN_SIZE",
which throws an error if you try to run a SQL query that MySQL's strategizer
thinks will require it to evaluate more than MAX_JOIN_SIZE rows. This is
intended to prevent the user from accidentally running giant queries that
will never finish, but some Mahara queries (which are large but will finish)
can trip it. Adding SQL_BIG_SELECTS=1 tels it that our queries are *not*
accidentally large.
Reviewed: https:/ /reviews. mahara. org/2869 gitorious. org/mahara/ mahara/ commit/ f4e4b44f8a414a3 4ff83ee9d863247 a80278040b
Committed: http://
Submitter: Son Nguyen (<email address hidden>)
Branch: 1.6_STABLE
commit f4e4b44f8a414a3 4ff83ee9d863247 a80278040b
Author: Aaron Wells <email address hidden>
Date: Mon Dec 16 13:57:38 2013 +1300
Override MySQL's check for accidental large queries
Bug 1070046: MySQL has an optional server config option, "MAX_JOIN_SIZE",
which throws an error if you try to run a SQL query that MySQL's strategizer
thinks will require it to evaluate more than MAX_JOIN_SIZE rows. This is
intended to prevent the user from accidentally running giant queries that
will never finish, but some Mahara queries (which are large but will finish)
can trip it. Adding SQL_BIG_SELECTS=1 tels it that our queries are *not*
accidentally large.
Also has order change for bug 1184450
Change-Id: I6db4699ea765d3 213d13eb93b8de0 98914db24e0