MySQL

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:

Enhancement

We have many place to use the exp/slices to sort our struct. It can improve performance by using pdqsort and clean branch check. But We have many placement using the old sort. Please remove it. Here is the example .

BTW, You haven't to change the bazel.build. it can be updated by robot.

• #36061
• #360

https://user-images.githubusercontent.com/24459435/179985397-7ffb4b43-fb30-40cd-a9ca-acae808a1d36.mov

At the moment, the name of the project is not included into the confirmation dialog. This can be very dangerous. It would be more helpful to include the name of the project into the dialog, like: "Do you want to delete the project "airtable-import-test"?

When browsing wide data tables in the dashboard (which I do a lot) it is very inconvenient because the browser's horizontal scrollbar is hidden unless you scroll to the very bottom of the page.
If I am at a page like /console/data/schema/public/tables/[tablename]/browse

I won't be able to scroll the table right (to see other columns) unless I first scroll vertically to the bottom of the page

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

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

This will allow specific database connection params to be used, like WAL mode on Sqlite, or CockroachDB options like serial_normalization etc.

Discussed in directus/directus#14153

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.

Our parser outputs all aggregations functions using the general sqlparser.FuncExpr. This is a little clunky and requires us to do additional checks before we are sure that the aggregation we have is valid and what it is aggregating.

I suggest we instead introduce one struct type per aggregation, and have them all implement some interface. This would help clean up the code.

Example:

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)