Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SET ... statement not supported #1945

Closed
shubhjet opened this issue Jan 12, 2024 · 1 comment
Closed

SET ... statement not supported #1945

shubhjet opened this issue Jan 12, 2024 · 1 comment

Comments

@shubhjet
Copy link

shubhjet commented Jan 12, 2024

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

set isolation to dirty read;
@manticore-projects 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 Apr 8, 2024
@manticore-projects
Copy link
Contributor

manticore-projects commented Apr 18, 2024

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.

@manticore-projects manticore-projects pinned this issue Apr 18, 2024
@manticore-projects manticore-projects changed the title [BUG] JSQLParser Version :4.7 : Informix SET ... TO ... ... not supported [BUG] Informix SET ... TO ... ... not supported Apr 18, 2024
@manticore-projects manticore-projects changed the title [BUG] Informix SET ... TO ... ... not supported SET ... statement not supported May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants