orm

Issue Creation Checklist

• I have read the contribution guidelines

Feature Description

When SQL errors occur, make the 'mes

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

Consider the following code (using AsChangeset instead / in addition to Insertable produces the same error message):

#[derive(Insertable)]
struct Foo {
        #[column_name = "type"]
        ty: String
}

This code is wrong because eventhough the table has a column called type, the auto-generated schema.rs file renames that to type_ to avoid using a keyword as an

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 (...)