-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Release notes for 374 #11402
Labels
Milestone
Comments
|
|
Above added with minor rewording |
# MongoDB
* Add support for [`CREATE SCHEMA`](/sql/create-schema) and [`DROP SCHEMA`](/sql/drop-schema). ({issue}`11409`) |
|
# MongoDB
* Add support for [`COMMENT ON TABLE`](/sql/comment). ({issue}`11424`) |
|
|
|
All above added. |
# Cassandra
* Add support for [TRUNCATE TABLE](/sql/truncate). ({issue}`11425`) |
Above added |
## SingleStore (MemSQL) connector
* The connector now uses the official [Single Store JDBC Driver](https://docs.singlestore.com/managed-service/en/developer-resources/connect-with-application-development-tools/connect-with-java-jdbc/the-singlestore-jdbc-driver.html).
As a result, `connection-url` in catalog configuration files needs to be updated from `jdbc:mariadb:...`
to `jdbc:singlestore:...`. ({issue}`10669`) |
# PostgreSQL
* Fix possible connection leak when connecting to PostgreSQL failed. ({issue}`11449`) |
Both added... |
# General
* Fix `trim`, `ltrim` and `rtim` function results when the argument is `char` type.
Previously, it returned padded results as `char` type. It returns `varchar` type without padding now. ({issue}`11440`) |
# SingleStore (MemSQL)
* Deprecate `memsql` as the connector name. We recommend using `singlestore` in the `connector.name` configuration property. ({issue}`11459`) |
# MongoDB
* Add support for [`COMMENT ON COLUMN`](/sql/comment). ({issue}`11457`) |
# MongoDB
* Support storing a comment when adding new columns. ({issue}`11487`) |
|
# ClickHouse
* Add support for `uint8`, `uint16`, `uint32` and `uint64` types. ({issue}`11490`) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: