SQL

Enhancement

[2022-02-14T04:12:14.746Z] ----------------------------------------------------------------------
[2022-02-14T04:12:14.746Z] FAIL: db_test.go:7069: testSerialDBSuite.TestModifyColumnTypeWhenInterception
[2022-02-14T04:12:14.746Z] 
[2022-02-14T04:12:14.746Z] db_test.go:7124:
[2022-02-14T04:12:14.746Z]     c.Assert(checkMiddleWarningCount, Equals, true)
[2022-02-14T04:12:

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

Working on a project I ran into the documentation for customizing the Foreign Key.
The docs read:

// https://sequelize.org/master/manual/assocs.html
// For example, to use UUID as the foreign key data type instead of the default (INTEGER), you can simply do:

const { DataTypes } = require("Sequelize");

Foo.hasOne(Bar, {
  foreignKey: {
    // name: 'myFooId'
    type: D

Describe the problem
When trying to use SHOW CREATE on a materialized view, the generated DDL is no longer a materialized view but a normal view, and the internal rowid column is part of the column definition.

To Reproduce

1. Create a materialized view:

CREATE MATERIALIZED VIEW test AS (SELECT 1 AS foo);

2. Use SHOW CREATE:

SHOW CREATE test

3. See tha

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.

Bug Description
taosBenchmark subscribe crash

To Reproduce
Steps to reproduce the behavior:

1. Build taosd, taosBenchmark in latest develop branch
2. go to 'TDengine/src/kit/taos-tools/example'
3. execute taosBenchmark -f insert_csv.json
4. execute taosBenchmark -f subscribe.json

Expected Behavior
taosBenchmark -f subscribe.json should not crash

Screenshots
N/A

Hi community,

This issue is for WeOpen-Star

We need to translate DistSQL cluster governance capabilities to English

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

The modulo operator works in Dolt:

> SELECT 2 % 2;
+-------+
| 2 % 2 |
+-------+
| 0     |
+-------+
> SELECT 2 MOD 2;
+-------+
| 2 MOD 2 |
+-------+
| 0     |
+-------+

But the MOD function is missing:

> SELECT MOD(2, 2);
function: 'mod, maybe you mean mid or md5?' not found

MySQL reference:
https://dev.mysql.com/doc/refman/8.0/en/mathematical-functions.h

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

The JSON response sent back over HTTP doesn't encode certain characters correctly.

For example, if a value in a string column contains the char \1 the byte value is copied verbatim in the response, breaking the client:

>>> json.loads('"\1"')
...
json.decoder.JSONDecodeError: Invalid control character at: line 1 column 2 (char 1)

Instead, we shou

• 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