orm

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

Microsoft.Data.Sqlite 6.0.1
TargetFramework net6.0-windows

当我创建一个字符串类型的SqliteParameter时，我查询它的类型，得到的类型信息是 “SqliteType.Integer”

var p = new Microsoft.Data.Sqlite.SqliteParameter("Name","123");

后来我在源码中定位到了以下位置，这就有点不合适了吧

https://github.com/dotnet/efcore/blob/8144d50ec0d15b87c35a9a3a425b1faadafb87f1/src/Microsoft.Data.Sqlite.Core/SqliteValueBinder.cs#L240-L263

• I have searched the issues of this repository and believe that this is

Original issue:

diesel-rs/diesel#3032

Relevant PRs:

diesel-rs/diesel#3035
diesel-rs/diesel#3036
diesel-rs/diesel#3037
diesel-rs/diesel#3092

Version

Other

What happened?

After I run migrations I run pg_dump to create the schema file (I tried adding a bunch of flags to reduce what gets put in there):

PGPASSWORD=postgres pg_dump -U postgres -h db -p 5432 --schema public --schema-only --no-tablespaces --no-subscriptions --no-security-labels --no-publications -x currencydb > database/structure.sql

Which has the

Hello,
I use postgres 12 with “MATERIALIZED” statement,
and I once asked on Discord how to use the “MATERIALIZED” statement in go-pg,
and get that is not support now.

Expected Behavior

WITH AS MATERIALIZED (...)