On Sun, 23 Oct 2005, Allie Micka wrote:
I suggest that you or somebody else who is interested in the issue simply tries to run current Drupal HEAD on such a hosting account and reports back.
FWIW, The default value for MySQL's Create_tmp_table_priv is 'N'.
Thanks, was afraid that would be the case.
Many shared hosting providers create a single administrative user with a GRANT ALL. While this is a bad idea, users on such a provider will not see any difference.
Yep.
Other hosting providers create administrative users and also site- specific users with minimal permissions. Odds are good that sites on these hosts will throw errors. We are in this category, and because roughly 1/3 of all sites we host use Drupal, we added the LOCK TABLES privilege to the list of site-user permissions. Frankly, I'm not too excited about adding yet another privilege to the list.
What is the problem with that permission? Use of storage space in /tmp?
So: +1 on using "big, bold letters" to highlight this issue in the docs +1 on donning flame-retardant attire and readying the fire extinguisher
And because I'm a fan of the "too many settings!" dialog gridlock, I'll pose a question: can the advanced search features be optional?
Yes, you can use trip_search instead. Or find a way to refactor the query in search.module. :) Look for occurrences of db_query_temporary. Cheers, Gerhard