MySQL

What happened:
Cloudwatch datasource, namespace AWS/ES metrics OpenSearchDashboard* do not fetch any results, because they have the wrong name:

If one manually creates a metric, ommiting the "(previously ...)" suffix, and does not use the default from the drop down, it works.

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

Recently reproduce many time in CI

https://ci.pingcap.net/blue/organizations/jenkins/tidb_ghpr_unit_test/detail/tidb_ghpr_unit_test/38976/pipeline/

[2022-03-04T03:58:22.683Z] ------------------------

Issue split from hasura/graphql-engine#6951

our pytest output has a pretty low signal:noise ratio, and it's often difficult to understand the cause of a test failure, if there is one. [Example: a 8600-line log for what turned out to be a flaky test that passed on a second run](https://app.circleci.com/pipelines/github/hasura/graphql-engine-mono/10008/workflows/5e17c7

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

Bug description

On windows, I run prisma format and note the unusual file ending. The lines are all LF, but the very last line is CRLF.

This causes issue on my Linux CI where it formats it ending in LF's only, causing a diff to occur and the build to fail.

How to reproduce

1. On windows do prisma format
2. Open in HxD or similar
3. See attached:

![image](https://user-images.g

Hi community,

This issue is for OpenForce 2022

Background

Previously, we needed to specify the worker-id when creating a snowflake key generator object.
But now that worker-id has been changed to a process-level configuration, there is no need to specify this parameter for each key generator.

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.

Preflight Checklist

• I have completed all Troubleshooting Steps.
• I'm on the latest version of Directus.
• There's no other issue that already describes my problem.

Describe the Bug

If you ca

Scenario:

• Single vttablet, connecting to external MySQL (happens to be RDS Aurora, but I doubt it matters).
• Single unsharded keyspace (keyspace3), no vschema, with a single table, containing a single row
• Test program using the Python pymysql driver, using the CLIENT.FOUND_ROWS flag, and updating a single row to it's current key value (i.e. no rows are updated, but a single row

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".