Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 0.7.0

Bug #4087 Comma not recognized after PRIMARY KEY statement
Submitted: 2005-04-06 19:47 UTC
From: epte at ruffdogs dot com Assigned: cybot
Status: Closed Package: SQL_Parser
PHP Version: Irrelevant OS:
Roadmaps: 0.5.1    
Comments Add Comment Add patch

Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
Solve the problem : 35 + 6 = ?

 [2005-04-06 19:47 UTC] epte at ruffdogs dot com
Description: ------------ This sql breaks: Reproduce code: --------------- CREATE TABLE `mpn_bannerfinish` ( `bid` int(11) NOT NULL auto_increment, `cid` int(11) NOT NULL default '0', `impressions` int(11) NOT NULL default '0', `clicks` int(11) NOT NULL default '0', `datestart` datetime default NULL, `dateend` datetime default NULL, PRIMARY KEY (`bid`), KEY `idxbannerfinishcid` (`cid`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1; Actual result: -------------- Parse error: Expected identifier on line 9 PRIMARY KEY (`bid`), ^ found: ","


 [2007-07-13 15:04 UTC] cybot (Sebastian Mendel)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on by the end of next Sunday (CET). If this was a problem with the website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.