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

https://github.com/sequelize/sequelize/blob/8a1429d6044123bba3a3f312b2e0c74b0c829990/lib/model.js#L1271

If I create any model with
charset: 'utf8mb4', collate: 'utf8mb4_general_ci'

sequelize translates it to this for mysql

CREATE TABLE IF NOT EXISTS tablename ... ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE utf8mb4_general_ci;

On stepping through the code, it seems that the issu

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.

There are several optimization the execution engine can perform when evaluating LIKE patterns with %, which matches zero or any number of any character. For example, see #80073.

Sequential %s can prevent these optimizations, but they are semantically equivalent to a single %, so the optimizer should normalize them to a single %.

For example:

-- The following expressions 

Bug Description
fix issues found by Coverity Scan in taosdump.c

To Reproduce
Steps to reproduce the behavior:
N/A

Expected Behavior
fix following issues found by Coverity Scan in taosdump.c

1. String not null terminated High TDengine/src/kit/taos-tools/src/benchUtil.c postProceSql
2. Resource leak High TDengine/src/kit/taos-tools/src/taosdump.c parse_json_to_recordschema
   3

Describe the Bug

To Reproduce

Make sure you have a lot of rows in a table and then change the table spacing to compact.

Errors Shown

None

What version of Directus are you using?

9.8.0

What version of Node.js ar

Hi community,

This issue is for WeOpen-Star

We need to add more unit test for DatabaseTypeEngine.

• DatabaseTypeEngine#getProtocolType
• DatabaseTypeEngine#getStorageType
• DatabaseTypeEngine#getDefaultSchemaName

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

Using dolt sql -q "<query>" -r csv > file.csv results in newlines in the output data:

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

Scenario

A user is ingesting some data (~300M rows) into a table with 270K distinct symbol values. For each of these 270K symbols we end up with at least one posix_fallocate() necessary to add a new value block. See the below flamegraph - it's quite illustrative.

An important part of the scenario is non-default index block capacity which is set to 2048. With the default capacity (w

• 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