Skip to content

Why DDL statements ignore database setting? #674

@x052bb

Description

@x052bb

Hi

Trying to upgrade to latest driver 0.3.1. We have a lot of DDL statements that don't have schema name explicitly set, now they all fail due to the following line in ClickHouseStatementImpl class:

boolean ignoreDatabase = parsedStmt.isRecognized() && !parsedStmt.isDML();

What is the reason for this? It seems very inconvenient to require explicit schema name in the SQL statement even if it is DDL.

For example, we have integration tests that use temporary created schema and then create required tables in it by running multiple "create table" scripts.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions