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

ClickHouse Export #112

Closed
wants to merge 2 commits into from
Closed

ClickHouse Export #112

wants to merge 2 commits into from

Conversation

adileo
Copy link

@adileo adileo commented May 16, 2024

  • Basic export for Clickhouse SQL supporting primary key/order by and Nullable fields
  • Added the possibility to specify a custom Data Type for a table field. (The <Select/> of the type is now open to custom user inputs, to evaluate if this is useful to other DB Engines)

To Do

Allow in the UI to select a specific flavour of DB Engine for a specific document, in this way we can show or hide fields or table configurations in the UI. Eg. On ClickHouse a table could support multiple Engine so there should be a way in the UI to specify that configuration on the table object. Or for example hide the "Types" tab in the UI since Clickhouse don't support those.

Copy link

vercel bot commented May 16, 2024

@adileo is attempting to deploy a commit to the dottle's projects Team on Vercel.

A member of the Team first needs to authorize it.

@1ilit
Copy link
Member

1ilit commented May 18, 2024

Hello, adding allowCreate and not adding the extra logic to handle types that appear neither in sqlDataTypes not obj.types will at least break the export feature for MySQL.

Also, I'm not very sure about supporting clickhouse natively at this point in time

@1ilit 1ilit closed this May 18, 2024
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 this pull request may close these issues.

None yet

2 participants