[drupal-devel] [bug] Table Prefix problem: test without prefix in 4.6RC passes

[chueewowee]

Issue status update for http://drupal.org/node/19595

 Project:      Drupal
 Version:      cvs
 Component:    base system
 Category:     bug reports
 Priority:     normal
 Assigned to:  Anonymous
 Reported by:  chueewowee
 Updated by:   chueewowee
 Status:       active

I'm updating the title here, as I switch post from version 4.52 to cvs
(my error). I cannot seem to ba able to edit the post


chueewowee



Previous comments:
------------------------------------------------------------------------

March 28, 2005 - 14:56 : chueewowee

Below follows the PHP error message:
Message
Table 'dr_drupal.dr_dr_term_data' doesn't exist query: SELECT * FROM
dr_dr_term_data WHERE tid = "13" in
/Volumes/Files/Users/chuee/Sites/drupal/includes/database.mysql.inc on
line 66.
Severity
error
My tables are prefixed with 'dr_'
The value $db_prefix = 'dr_'; has been inserted into settings.php
An example of the actual tables from the database.mysql can be seen to
be:
-- Table structure for table 'term_hierarchy'
create table dr_term_hierarchy (
  tid int(10) unsigned NOT NULL default '0',
  parent int(10) unsigned NOT NULL default '0',
  KEY tid (tid),
  KEY parent (parent)
) TYPE=MyISAM;
When checking all tables in through the dba.module, similar errors are
given for non-core modules such as store.module. So the arror applies
accross the board.
The behaviour when creating content is like this: A post is accepted
for publication according to inspection of the content list, and as
according the log, eg.: 
page: added test conspiracy content.
Severity
notice
Hostname
127.0.0.1), . 
However when clicking on a category term to view publications in the
category browser, a blank pageis returned. When a category has no posts
a normal page with message is displayed: 'There are currently no posts
in this category.' 
John Plum


------------------------------------------------------------------------

March 28, 2005 - 15:25 : chueewowee

Attachment: http://drupal.org/files/issues/dr_mightyz-mightyzero.sql (195.39 KB)

I tried the same database, but stripped the prefix and all works ok. The
bug occured with the latest 4.6RC  version.
I am attaching a database with the prefix dr_ attached to all tables
for your convenience.