Closed (duplicate)
Project:
Drupal core
Version:
7.x-dev
Component:
database system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
29 Mar 2010 at 19:52 UTC
Updated:
20 May 2010 at 09:48 UTC
Jump to comment: Most recent file
Comments
Comment #1
aspilicious commentedCan you tell us more bout the technical specs of the hosting company. (php version, ...)
Comment #2
kgaut commentedSure, I've tried with :
PHP 5.3 and 5.2.12
MySQL 5.0.51
Comment #3
SebCorbin commentedIf this can help...
Comment #4
Crell commentedMySQL 5 should always have an information_schema database as far as I know. If it doesn't then the DB is broken beyond Drupal's help. I'd expect a more conventional error as well if there were a table or DB missing.
Does that query work if run outside of Drupal? If run as a non-prepared-statement?
Comment #5
kgaut commentedI just tried this query and got the following error:
#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ':db_condition_placeholder_4) AND (table_name = :db_condition_placeholder_5)LIM' at line 1
Comment #6
Crell commentedWell it's not going to take a literal prepared statement. :-) You need to insert in the appropriate values for the two placeholders, with quotes as appropriate.
Comment #7
x3cion commentedMaybe I didn't see it, but did you mention if you use webhosting or run an own root server?
Anyway, for :db_condition_placeholder_4 you should use a database the user has access to and for :db_condition_placeholder_5 you should use a table inside this database.
Comment #8
kgaut commentedOk,
Now it's working on ovh.
Got that:
| 1 |
| 1 |
Comment #9
SebCorbin commentedThe thing is, in shared hosting we only have access to our database, not information_schema (unless you are on provate hosting) so query on information_shema database will fail.
Crell: I tried the query (with replaced placeholders) and it failed (under phpmyadmin), because permission to view information_schema are not granted, and we cannot get it granted.
Comment #10
damien tournoud commentedI'm pretty sure this is nothing more then a performance issue. OVH runs several thousand databases on its clusters, and the information schema scales much worse then we anticipated. Tentatively marking this as a duplicate of #748340: MySQL-optimized tableExists() implementation.
See also #686196: Meta issue: Install failures on various hosting environments for some additional discussions.
Comment #11
kgaut commentedThe problem is solved in D7a4