SQL

Issue Creation Checklist

• I have read the contribution guidelines

Feature Description

When SQL errors occur, make the 'mes

Sometimes it is needed to store compressed data in the DB. Unfortunately not all the DBs have built-in compression and FUSE compressed FSes are not available for every OS. So it may make sense to store compressed binary blobs in the DB.

Unfortunately when one sees them in DBeaver he sees them compressed, but often they are needed uncompressed. So it'd be nice to have a feature to decompress the

Please consider adding a way to control which nodes participate in an IMPORT operation so that nodes in far regions can be excluded from the import.

Consider a 3-region cluster, with nodes in: [Japan, US West, EU]. And let's import a table into a database that has only a primary region defined in US West. All of the table's replicas will be located in US West. And the CSV data to be imported is

We already have some scripts in the scripts directory. It would be good to run them for every PR.
This is also a great task for beginners.

In https://github.com/taosdata/TDengine/blob/develop/src/client/src/tscPrepare.c, Local variable loopCont is assigned only once, to a constant value, making it effectively constant throughout its scope. If this is not the intent, examine the logic to see if there is a missing assignment that would make loopCont not remain constant.

So the 1567th line should be removed.
![image](https://user-im

    @Test
    public void assertMethod() {
        assertThat(h2Repository.getType(), is("H2"));
        assertSetProperty();
        assertPersistAndGet();
        assertPersistAndGetChildrenKeys();
        assertDelete();
        h2Repository.close();
    }

Splitting assertMethod() method.

Currently we only support Upsert for CockroachDB. Implementing same for MySQL should be pretty straightforward as well.

Wonder if we can also use INSERT ON CONFLICT UPDATE for PostgreSQL to ensure operation with same signature also works.

Describe the bug
Using a time dimension on a runningTotal measure on Snowflake mixes quoted and unquoted columns in the query. This fails the query, because Snowflake has specific rules about quoted columns. Specifically:

• All unquoted column names are treated as upper case
• Quoted column names are case sensitive.

So "date_from" <> date_from

To Reproduce
Steps to reproduce

Issue description

This option will improve performance in many scenarios
https://dev.mysql.com/worklog/task/?id=8134

https://www.facebook.com/weixiang.zhai/posts/678596755543802

When I try to connect dolt server using golang's go-sql-driver/mysql driver in multiple heads mode, It seems that go-sql-driver/mysql driver does't support database with a sub name. DSN string format in go-sql-driver/mysql like [username[:password]@][protocol[(address)]]/dbname[?param1=value1&...&paramN=valueN]. When dbname is "mydb", It works, but not work when dbname is "mydb/feature-branch".

Describe the Bug

Sending invalid GUIDs to API endpoints will cause them to return an error code "500 Internal Server Error".

Steps To Reproduce

1. HTTP DELETE to API endpoint such as /api/emergency-access/ with invalid GUID like "asd"

Expected Result

Endpoint returns a "400 Bad Request"

Actual Result

Endpoint returns a "500 Internal Server Error"

Environment

Hi all. Congrats for the amazing software :)

Is your feature request related to a problem? Please describe.

It would be amazing to have the IN operator available in this drop-down list:

Describe the solution you'd like

Have the IN oper

Describe the bug

Currently keys written to server.conf go undetected.

This means that not only typos go undetected, but lack of validation is a risk during version migration as settings that used to apply in a previous version have no effect in a newer one without warning -- even if new settings are supposed to be used.

To reproduce

• Create a key with a typo.
• Watch the QuestDB

• Missing information on how to create other databases
• Missing information on how to switch to other databases
• When using time travel, we don’t know where to get the transaction number from - we should show this to the user after committing data (this may be a missing capability in immudb / tools).
• The last long query example in the quick start is incorrect (incorrect