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 — `SET ...` statement not supported · Issue #1945 · JSQLParser/JSqlParser

SET ... statement not supported #1945

New issue
Copy link
New issue
Copy link
Closed
Closed
SET ... statement not supported#1945
Copy link
Labels
Sponsor neededexotic

Description

@shubhjet
shubhjet
opened on Jan 12, 2024
Issue body actions

I am using Informix and JSQParser to parse the SQL statements.:

set isolation to dirty read;

Activity

  1. manticore-projects
    added
    exotic
    Sponsor needed
    on Jan 12, 2024
  2. manticore-projects
    changed the title [-][BUG] JSQLParser Version :4.7 : Failing to parse informix isolation level statement[/-] [+][BUG] JSQLParser Version :4.7 : Informix `SET ... TO ... ...` not supported[/+] on Apr 8, 2024
  3. manticore-projects commented on Apr 18, 2024

    @manticore-projects
    manticore-projects
    on Apr 18, 2024
    Contributor
    More actions

    Greetings.

    With latest JSQLParser-4.10 Snapshot, you can parse your RDBMS specific statement like:

    String sqlStr = "set isolation to dirty read;";
    Statement statement = CCJSqlParserUtil.parse(
            sqlStr,
            parser -> parser.withUnsupportedStatements(true) );
    Assertions.assertInstanceOf(UnsupportedStatement.class, statement);
    TestUtils.assertStatementCanBeDeparsedAs(statement, sqlStr, true);

    This should be good enough for anything, that is not a Query or a DML or a standard compliant DDL -- unless there was a very strong reason to access the details of the statement.
    I am going to close most RDBMS specific DDL issues in this regard.

  4. manticore-projects
    pinned this issue on Apr 18, 2024
  5. manticore-projects
    changed the title [-][BUG] JSQLParser Version :4.7 : Informix `SET ... TO ... ...` not supported[/-] [+][BUG] Informix `SET ... TO ... ...` not supported[/+] on Apr 18, 2024
  6. manticore-projects
    closed this as completedon Apr 18, 2024
  7. manticore-projects
    changed the title [-][BUG] Informix `SET ... TO ... ...` not supported[/-] [+]`SET ...` statement not supported[/+] on May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Sponsor neededexotic

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — 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.