Bug #53759 Error Message TOLD me to report this bug
Submitted: 18 May 2010 18:57 Modified: 26 May 2010 21:31
Reporter: Jason Sage Email Updates:
Status: Unsupported Impact on me:
None 
Category:MySQL Administrator Severity:S2 (Serious)
Version: OS:Any
Assigned to: CPU Architecture:Any

[18 May 2010 18:57] Jason Sage
Description:
Exported database using MySQL Admin GUI in Windows XP SP3 version: 1.2.11 (Connected to CentOS 32bit linux running: mysql  Ver 14.12 Distrib 5.0.45, for redhat-linux-gnu (i386) using readline 5.0)

Imported Database Using MySQL Admin GUI in Windows XP SP3 version: 1.2.11 
(Connected to CentOS 32bit Linux running: mysql  Ver 14.12 Distrib 5.0.77, for redhat-linux-gnu (i686) using readline 5.1)

Error message received via MySQL Admin during restore:

Message BEGIN-----
Warning: Do not know how to handle this statement at line 174:
INSERT INTO `#__categories` (`id`,`parent_id`,`title`,`name`,`alias`,`image`,`section`,`image_position`,`description`,`published`,`checked_out`,`checked_out_time`,`editor`,`ordering`,`access`,`count`,`params`) VALUES 
 (27,0,'New to Joomla!','','new-to-joomla','','3','left','Questions for new users of Joomla!',1,0,'0000-00-00 00:00:00',NULL,3,0,0,''),
 (30,0,'The Community','','the-community','','4','left','About the millions of Joomla! users and Web sites<br />',1,0,'0000-00-00 00:00:00',NULL,3,0,0,''),
 (31,0,'General','','general','','3','left','General questions about the Joomla! CMS',1,0,'0000-00-00 00:00:00',NULL,1,0,0,''),
 (32,0,'Languages','','languages','','3','left','Questions related to localisation and languages',1,0,'0000-00-00 00:00:00',NULL,4,0,0,''),
 (33,0,'Joomla! Promo','','joomla-promo','','com_banner','left','',1,0,'0000-00-00 00:00:00',NULL,1,0,0,'');
Ignoring this statement. Please file a bug-report including the statement if this statement should be recognized.
Warning: Do not know how to handle this statement at line 180:
/*!40000 ALTER TABLE `#__categories` ENABLE KEYS */;
Ignoring this statement. Please file a bug-report including the statement if this statement should be recognized.
Warning: Do not know how to handle this statement at line 188:
CREATE TABLE `#__components` (
  `id` int(11) NOT NULL auto_increment,
  `name` varchar(50) NOT NULL default '',
  `link` varchar(255) NOT NULL default '',
  `menuid` int(11) unsigned NOT NULL default '0',
  `parent` int(11) unsigned NOT NULL default '0',
  `admin_menu_link` varchar(255) NOT NULL default '',
  `admin_menu_alt` varchar(255) NOT NULL default '',
  `option` varchar(50) NOT NULL default '',
  `ordering` int(11) NOT NULL default '0',
  `admin_menu_img` varchar(255) NOT NULL default '',
  `iscore` tinyint(4) NOT NULL default '0',
  `params` text NOT NULL,
  `enabled` tinyint(4) NOT NULL default '1',
  PRIMARY KEY  (`id`),
  KEY `parent_option` (`parent`,`option`(32))
) ENGINE=MyISAM AUTO_INCREMENT=34 DEFAULT CHARSET=utf8;
Ignoring this statement. Please file a bug-report including the statement if this statement should be recognized.
Warning: Do not know how to handle this statement at line 210:
/*!40000 ALTER TABLE `#__components` DISABLE KEYS */;
Ignoring this statement. Please file a bug-report including the statement if this statement should be recognized.
Warning: Do not know how to handle this statement at line 211:
INSERT INTO `#__components` (`id`,`name`,`link`,`menuid`,`parent`,`admin_menu_link`,`admin_menu_alt`,`option`,`ordering`,`admin_menu_img`,`iscore`,`params`,`enabled`) VALUES 
 (1,'Banners','',0,0,'','Banner Management','com_banners',0,'js/ThemeOffice/component.png',0,'track_impressions=0\ntrack_clicks=0\ntag_prefix=\n\n',1),
 (2,'Banners','',0,1,'option=com_banners','Active Banners','com_banners',1,'js/ThemeOffice/edit.png',0,'',1),
 (3,'Clients','',0,1,'option=com_banners&c=client','Manage Clients','com_banners',2,'js/ThemeOffice/categories.png',0,'',1),
 (4,'Web Links','option=com_weblinks',0,0,'','Manage Weblinks','com_weblinks',0,'js/ThemeOffice/component.png',0,'show_comp_description=1\ncomp_description=\nshow_link_hits=1\nshow_link_description=1\nshow_other_cats=1\nshow_headings=1\nshow_page_title=1\nlink_target=0\nlink_icons=\n\n',1),
 (5,'Links','',0,4,'option=com_weblinks','View existing weblinks','com_weblinks',1,'js/ThemeOffice/edit.png',0,'',1),
 (6,'Categories','',0,4,'option=com_categories&section=com_weblinks','Manage weblink categories','',2,'js/ThemeOffice/categories.png',0,'',1),
 (7,'Contacts','option=com_contact',0,0,'','Edit contact details','com_contact',0,'js/ThemeOffice/component.png',1,'contact_icons=0\nicon_address=\nicon_email=\nicon_telephone=\nicon_fax=\nicon_misc=\nshow_headings=1\nshow_position=1\nshow_email=0\nshow_telephone=1\nshow_mobile=1\nshow_fax=1\nbannedEmail=\nbannedSubject=\nbannedText=\nsession=1\ncustomReply=0\n\n',1);
Ignoring this statement. Please file a bug-report including the statement if this statement should be recognized.
Warning: Do not know how to handle this statement at line 219:
Message END----

How to repeat:
You'd have to import my joomla database backup to recreate this. It's named: joomla_www_neproclub_org.sql
I'll gladly send it to ya (if you request in a reasonably soon timeframe)

Suggested fix:
Don't allow folks to make entities named with a pound (#) sign I suppose.
[19 May 2010 5:45] Jason Sage
I was in the middle of moving many websites when I filed this: I was in a hurry. After looking over this again; I realized the error message said "submit bug report IF the (syntax of the SQL code) statement should be recognized.

I still think this is a valid report however because the joomla database I backed up and tried to restore worked fine prior to doing the steps outlined in my description of what I was doing when I ran into this. I can only theorize at this point however some facts for ya:

In the original database which I still have;(before backing it up) there are like 35 tables with the #__ prefix (pound sign followed by two underscores). The ERROR message however only complains of a couple entities (and an insert). 

Looking at the final result (the database after import) - I can not see any tables at all with the odd #__ prefix (pound sign followed by two underscores).
I suspect they either all failed or are "deleted" tables or something that simply shouldn't of been exported in the first place. 

I'll let you MySQL developers give it scrutiny; I'm not too familiar with MySQL's inner workings. I'm just sharing what info I have that might help.

Great Database system though: I love it!
[26 May 2010 21:31] MySQL Verification Team
Thank you for the bug report. MySQL Administrator isn't more supported please use the Workbench instead. Thanks in advance.