Skip to content

Missing error response #13

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

Closed
ceckoslab opened this issue Aug 26, 2024 · 3 comments · Fixed by #14
Closed

Missing error response #13

ceckoslab opened this issue Aug 26, 2024 · 3 comments · Fixed by #14

Comments

@ceckoslab
Copy link

I've been playing with chdb and I was experimenting with creating tables.

I did a mistake while creating the following table:

const createSql = `CREATE TABLE IF NOT EXISTS invalid_create_table (id Int32)
ENGINE = MergeTree()
PARTITION BY (id)
SETTINGS index_granularity = 8192;`

const res = session.query(createSql);
console.log(res);

The console.log(res); returns empty result and not indication for an error.

Where the ClickHouse playground returns:

Code: 36. DB::Exception: You must provide an ORDER BY or PRIMARY KEY expression in the table definition. If you don't want this table to be sorted, use ORDER BY/PRIMARY KEY (). Otherwise, you can use the setting 'create_table_empty_primary_key_by_default' to automatically add an empty primary key to the table definition. (BAD_ARGUMENTS) (version 24.4.4.113 (official build))

Am I doing something wrong is is this a real bug/issue?

@auxten
Copy link
Member

auxten commented Aug 27, 2024

Sorry, it's a chdb-node bug issue.
It's still using the old chdb C API, I will update it to the v2 API to fix that this week.

@ceckoslab
Copy link
Author

@auxten no worries, happy report and find any other possible bugs! I love chdb :)

@ceckoslab
Copy link
Author

Also for the record, I am running it on Mac M2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants
@auxten @ceckoslab and others