SQL

Enhancement

mysql> CREATE TABLE t1 (
    -> risk_id varchar(32) NOT NULL,
    -> tran_id int NOT NULL,
    -> KEY (`risk_id`)
    -> );

mysql> CREATE TABLE t2 (
    -> risk_id varchar(32) COLLATE utf8mb4_general_ci NOT NULL,
    -> -- risk_id varchar(32) NOT NULL,
    -> tran_id int NOT NULL,
    -> KEY (`risk_id`)
    -> );

mysql> explain select /*+ hash_join(t1) */ t1.ris

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.

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

In a support escalation (https://github.com/cockroachlabs/support/issues/1709) for a v21.1 cluster, we saw that leaked gossip entries could impact foreground latency. The gossip leak itself has [since been fixed](cockroachdb/cockroach@d07b32db3e49e

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

To Reproduce
N/A

Expected Behavior
fix following issues:
| issue type | category | file path | function | line number |
| -------------------------- | -------------------------- | -------------------------- | -------------------------- |

Describe the Bug

I've got a bizarre behavior using Flows and Webhook / Request URL operation (https://docs.directus.io/configuration/flows/operations/#webhook-request-url)

If I put in the Request body {{ $trigger}}

the content-type of the request is **applica

FAQ page always changes, but the document is pretty static.
It is better to split FAQ and document, just remove FAQ and move the content into GitHub Wiki.

The tasks are:

• Add FAQ page in GitHub Wiki;
• Move FAQ content into WIKi;
• Add FAQ link into homepage's top menu (in document section);
• Add FAQ link into homepage's bottom menu (in document section).

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

Currently, when you clone a single branch from a Dolt database, you get only that single branch, but you still get remote tracking branches for the other branches in the remote database. To follow Git's semantics, we should not be creating those remote tracking branches for other branches.

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

Is your feature request related to a problem? Please describe.
with the implementation of copy to clipboard it would be very useful to have the option to copy with this pattern below (which I don't remember the name at this time)

Is your feature request related to a problem?

We have users periodically asking for week-based partitioning.

Describe the solution you'd like.

Add WEEK to the PARTITION BY options.

Describe alternatives you've considered.

No response

Additional context.

This PR should give enough hints on how to implement this feature: questdb/questdb#1571

안녕하세요

자료 보면서 공부하다가 counting sort 코드가 이상한 부분이 있어서 수정했습니다

1. 과정 3에서 누적합을 만들어줄 때 arr.length -> counting.length
2. 과정 4에서 다시 sorted_arr에 넣어줄 때 인덱스가 counting[arr[i]] -> counting[arr[i]] - 1

좋은자료 항상 감사합니다 :)