I submitted a bug previously, but can't find it.

I received the following when trying to update my 6.19 to 7.x beta:

DatabaseSchemaObjectExistsException: Table cache_path already exists. in DatabaseSchema->createTable() (line 621 of /home/myname/public_html/books/includes/database/schema.inc).

Is there anyway I can update the database manually to continue the update?

Comments

damien tournoud’s picture

Status: Active » Closed (duplicate)
shelleyp’s picture

Status: Closed (duplicate) » Active

This is NOT a Pressflow site. This is NOT a duplicate bug. This is NOT a fork, I am using straight and unmodified Drupal.

Please do not close this bug because of vague similarities.

Now I know why I couldn't find the other bug. You shouldn't have closed this bug until I concurred that it was a duplicate, or you had more facts.

If I had a failed update, would this type of error have occurred? It shouldn't. The update/install should be intelligent enough to test for an incomplete state and either repair or remove the table.

And I couldn't find this table in my database, either.

damien tournoud’s picture

Well. You *do* have a cache_path in your database, right? Where does it come from?

shelleyp’s picture

Nope, I don't. But I keep getting this error.

I don't know what to do, and I don't know why I'm getting it.

I even found my original bug, and someone had suggested the following:

DROP TABLE cache_path;
DROP INDEX system_list ON system;

Tried this, and got an error: cache_path does not exist.

And yes, I am looking at the correct database.

damien tournoud’s picture

This is the first table actually created by Drupal, so I guess you are actually bumping into something like #818374: Add a requirements check error if PECL PDO is being used.

You need proper PHP PDO to install Drupal 7, PDO installed via PECL will not work. Try to apply the patch in #818374-8: Add a requirements check error if PECL PDO is being used and see if you bump into a requirement error.

shelleyp’s picture

I tried the patch, and I am now getting:

PDO is not the correct version!

Drupal 7 requires the PHP Data Objects (PDO) extension from PHP core to be enabled. The version installed on this system is from PECL.

See the system requirements page for more information.

I have a ticket into my hosting company to install the extension from core.

This one is going to generate problems for people. Especially who aren't programmers. Thanks for pointing out what the problem really is.

Once the correct PDO is installed, I'll try again and update this bug with the results.

shelleyp’s picture

I've heard from my ISP.

Until recently, they couldn't install this because of cPanel. That's been fixed, but they're going to have to do some serious testing with SQLite3 and PostgreSQL in order to ensure this isn't going to break other applications on the machine.

They also mentioned something about how nice it would be if Drupal gave us an option to select mysqli support.

I have a strong feeling this is going to be a major point of failure for the Drupal 7 roll out.

Until my system can be upgraded, I'll leave this bug open. It is a duplicate of the PECL bug, but others will have this same message. It might help them figure out what's happening.

greggles’s picture

I think it makes sense to close this bug now as a duplicate of one of the items in #5.

This issue is already the first result in google for the error message:

http://www.google.com/search?q=DatabaseSchemaObjectExistsException%3A%20....

or even fragments of the error http://www.google.com/search?num=100&hl=en&q=Table+cache_path+already+ex...

or drupal.org search finds it pretty well: http://drupal.org/search/apachesolr_search/Table%20cache_path%20already%....

I think people will be able to find it by using a search tool and that leaving it open is not accurate to the problem nor particularly helpful for people trying to find the issue.

damien tournoud’s picture

Status: Active » Closed (duplicate)