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/2804 gitorious. org/mahara/ mahara/ commit/ 03f4ecd39601a66 d5926fee9fbe81b 1aff90f8a4
Committed: http://
Submitter: Robert Lyon (<email address hidden>)
Branch: master
commit 03f4ecd39601a66 d5926fee9fbe81b 1aff90f8a4
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.
Change-Id: I6db4699ea765d3 213d13eb93b8de0 98914db24e0