Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

CREATE TABLE statement not properly parsed or build

Open
#256 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
mysql, php, sql

Research direction

Start with the PHP reproduction using Parser and statements[0]->build(), then inspect how the MySQL versioned comment in the CREATE TABLE statement is tokenized and rendered. Done means the generated SQL no longer includes the comment's closing marker after DEFAULT NULL, with regression coverage for this example.

Written by the indexing model from the issue text.

Description

bug help wanted
$sql    = 'CREATE TABLE tab1 (`col1` TIMESTAMP /*!40100 DEFAULT NULL */)';
$parser = new Parser($sql);
$s3     = $parser->statements[0]->build();
// $s3 wrongly contains end-of-comment
// CREATE TABLE tab1 (
//  `col1` timestamp DEFAULT NULL */
//)

//PHP 7.1.18
//"name": "phpmyadmin/sql-parser",
//"version": "5.0.0",
Dominant language
PHP
Stars
485
Forks
119
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from phpmyadmin/sql-parser

All issues in phpmyadmin/sql-parser

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.