MySQL

The annotation loading spinner that on 8.3.6 was on the same line as the annotation label/toggle, has now, since updating to 8.4.1 started wrapping onto another line, pushing the graphs down to make space. On a dashboard with a frequent refresh time this make the graphs jump up and down a lot!! See screen recording:

![vid](https://user-images.githubusercontent.com/2304970/154947127-8c83f8b4-ff6

Describe the bug
At the time of registration, email has not been validated correctly http://localhost:1337/admin/auth/register

Expected behavior
An email should be valid in all aspect like

• should check valid domain, well-formed and valid mailbox

Screenshots
invalid email1:

lightning v5.3.0

After the content in parquet may be written by spark, the definition of bool is true or false. Regenerating the parquet file takes time, In tidb, bool behaves as tinyint, so proper type conversion will help improve the success rate of lightning import

parquet file：
![image](https://user-images.githubusercontent.com/21033020/147809823-214dcb34-0e10-4566-aa75-2109c0525144

Issue Creation Checklist

• I have read the contribution guidelines

Feature Description

When SQL errors occur, make the 'mes

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

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

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.

To match https://docs.directus.io/reference/files/#import-a-file

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

Can't use 'Comment' as column alias.
To reproduce:

$ dolt version
dolt version 0.37.0
$ dolt init
$ dolt sql
Dolt>  SELECT TABLE_COMMENT AS Comment FROM information_schema.TABLES;
Error parsing SQL
syntax error at position 32 near 'Comment'
SELECT TABLE_COMMENT AS Comment FROM information_schema.TABLES
                                ^
Dolt>