user warning: Table 'client_drpl1.cache_views' doesn't exist query ?|? [#143294]

When installing module VIEW in the drupal happens the following error:

# user warning: Table 'araripina_drpl1.cache_views' doesn't exist query: SELECT data, created, headers, expire FROM cache_views WHERE cid = 'views_urls' in /home/araripina/public_html/saojoao/includes/database.mysql.inc on line 172.
# user warning: Table 'araripina_drpl1.cache_views' doesn't exist query: SELECT data, created, headers, expire FROM cache_views WHERE cid = 'views_default_views:pt-br' in /home/araripina/public_html/saojoao/includes/database.mysql.inc on line 172.
# user warning: Table 'araripina_drpl1.cache_views' doesn't exist query: SELECT data, created, headers, expire FROM cache_views WHERE cid = 'views_tables:pt-br' in /home/araripina/public_html/saojoao/includes/database.mysql.inc on line 172.
# user warning: Table 'araripina_drpl1.cache_views' doesn't exist query: LOCK TABLES cache_views WRITE in /home/araripina/public_html/saojoao/includes/database.mysql.inc on line 172.

I tried the version new and also it returned the same error. How I must proceed to correct this error? I observed that it does not obtain to execute a command sql, what I make?

Comment	File	Size	Author
	bug_1.gif	25.03 KB	zerutreck

Comments

Comment #1

merlinofchaos commented 11 May 2007 at 17:29

Status:

Active

» Fixed

You should try this with -beta5 which fixed all of these errors.

Comment #2

zerutreck commented 11 May 2007 at 17:55

As I spoke above, I already tested with the version most recent and I happened ERROR THE SAME.

Comment #3

zerutreck commented 11 May 2007 at 18:11

Status:

Fixed

» Postponed (maintainer needs more info)

Exactly with version 5 the problem persists. How I make I am correction?

Comment #4

merlinofchaos commented 11 May 2007 at 18:15

Did you run update.php?

Comment #5

zerutreck commented 11 May 2007 at 23:08

Status:

Postponed (maintainer needs more info)

» Fixed

thanxs, my problem solved.

Comment #6

(not verified) commented 25 May 2007 at 23:31

Status:

Fixed

» Closed (fixed)

Comment #7

M.J. Taylor commented 7 September 2007 at 22:22

Status:

Closed (fixed)

» Active

This is still an issue through views-5.x-1.6-beta5.tar.gz and views-5.x-1.6.tar.gz

Running update doesn't fix it in all cases, because update is somehow skipping

views module
Update #14
CREATE TABLE {cache_views} ( cid varchar(255) NOT NULL default '', data longblob, expire int NOT NULL default '0', created int NOT NULL default '0', headers text, PRIMARY KEY (cid), INDEX expire (expire) ) /*!40100 DEFAULT CHARACTER SET UTF8 */
DELETE FROM {cache_views}

How exacty I don't know.

MY fix was to run update again and manually set Views to Update #14, which creates the cache_views table and stops the error messages... It will spit errors on Update #15, since it's somehow already done that, but you can ignore those.

Changing status back to active so the maintainer can correct the Update structure/path.

Comment #8

ceo3141 commented 28 May 2008 at 01:33

Hi,
I had the same problem w Views 5.x-1.6. You said your solution was
"run update again and manually set Views to Update #14, which creates the cache_views table and stops the error messages"
1) Drupal tells you to run update.php only once . . . will bad things happen to me if I run it again?
2) How exactly do you "manually set Views to Update #14"? Excuse my newbie question, I just don't know what that means . . . what exactly do I do after I run update.php again?
I greatly appreciate any help -- thank you in advance.