I've just installed Drupal 7, created a new database and downloaded some modules but the only one currently active is schema. When I go to Structure -> Schema this error message appears:

PDOException: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens: SELECT * FROM information_schema.COLUMNS WHERE table_catalog=:database AND table_schema=current_schema()ORDER BY table_name, ordinal_position; Array ( [:database] => mybase [:table] => ) in schema_compare_schemas() (line 221 of /var/www/html/drupal/sites/all/modules/schema/schema.module).

Anyone have an idea about what is going on here?

Comments

sunnydeveloper’s picture

sunnydeveloper commented

I got a different error testing this out":

Notice: Undefined index: warn in schema_compare() (line 614 of C:\workspace\drupal7\sites\all\modules\schema\schema.module).
Warning: Invalid argument supplied for foreach() in schema_compare() (line 615 of C:\workspace\drupal7\sites\all\modules\schema\schema.module).
Notice: Undefined index: extra in schema_compare() (line 623 of C:\workspace\drupal7\sites\all\modules\schema\schema.module).
Notice: Undefined index: extra in schema_compare() (line 633 of C:\workspace\drupal7\sites\all\modules\schema\schema.module).

what version of schema did you install?

sunnydeveloper’s picture

sunnydeveloper commented

although I was using mysql..

Khellus’s picture

Khellus commented

I've tried both 7 versions, beta and dev; same error. There are lots of similar errors if you google parts of the error message, so I don't believe anyone has an answer to this issue.

kars-t’s picture

kars-t commented
Status: Active » Fixed

Dear fellow Drupal enthusiasts,

this issue is now lasting for a very long time in the issue queue and was unfortunately never solved. As Drupal is a open source project everyone is helping on voluntary basis. So that this is was not solved is nothing personal and means no harm. But perhaps no one had time to deal with this issue, maybe it is too complex or did not pose the problem comprehensible.

But this issue is not the only one. There are thousands of issues on Drupal.org that have never been worked on or could not be processed. This means that we are building a wave that is unmanageable and just a problem for the Drupal project as a whole. Please help us keep the issue queue smaller and more manageable.

Please read again, "Making an issue report" and see if you can improve the issue. Test the problem with the current Core and modules. Maybe the problem doesn't exist anymore, is a duplicate or has even been solved within this issue but never closed.

Help can also be found for it on IRC and in the user groups.

In order this issue no longer remains, I put this issue to "fixed".

If there is new information, please re-open the issue.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.