GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — parse "CURRENT_TIMESTAMP(3)" error · Issue #1507 · JSQLParser/JSqlParser

parse "CURRENT_TIMESTAMP(3)" error #1507

New issue
Copy link
New issue
Copy link
Closed
#1666
Closed
parse "CURRENT_TIMESTAMP(3)" error#1507
#1666
Copy link
Assignees
manticore-projects
Labels
improvement

Description

@patinousward
patinousward
opened on Apr 8, 2022
Issue body actions

CCJSqlParserUtil.parse("update btrip_payment set update_time = CURRENT_TIMESTAMP(3) where id = 1");

version:4.2

image

Activity

  1. wumpz commented on Apr 9, 2022

    @wumpz
    wumpz
    on Apr 9, 2022
    Member
    More actions

    JSqlParser only supports CURRENT_TIMESTAMP without parameters. Which database supports this?

  2. patinousward commented on Apr 11, 2022

    @patinousward
    patinousward
    on Apr 11, 2022
    Author
    More actions

    JSqlParser only supports CURRENT_TIMESTAMP without parameters. Which database supports this?

    mysql support

  3. wumpz commented on Apr 11, 2022

    @wumpz
    wumpz
    on Apr 11, 2022
    Member
    More actions

    Any chance you want to provide a PR?

  4. manticore-projects commented on Jun 4, 2022

    @manticore-projects
    manticore-projects
    on Jun 4, 2022
    Contributor
    More actions

    Actually, it is just a Keyword problem again: When <K_TIME_KEY_EXPR> was explicitly allowed as Function Name, then CURRENT_TIMESTAMP(3) would be read as a Function and parsed properly.

    The Keyword PR #1382 solves this problem.

  5. manticore-projects
    self-assigned this
    on Nov 14, 2022
  6. manticore-projects
    added
    improvement
    on Nov 14, 2022
  7. manticore-projects
    added a commit that references this issue on Nov 14, 2022

    fix: White-list CURRENT_DATE and CURRENT_TIMESTAMP tokens

    This issue will close once commit 9df3c07 is merged into the 'master' branch.
    9df3c07
  8. wumpz
    closed this as completedin #1666on Nov 20, 2022
  9. wumpz
    added a commit that references this issue on Nov 20, 2022

    Assorted fixes (#1666)

    This issue will close once commit bff268a is merged into the 'master' branch.
    bff268a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

  • @manticore-projects
    manticore-projects

Labels

improvement

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    You are visitor 01402520 — GeezerVison does not store the pages you look up.
    Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.