orm

Working on a project I ran into the documentation for customizing the Foreign Key.
The docs read:

// https://sequelize.org/master/manual/assocs.html
// For example, to use UUID as the foreign key data type instead of the default (INTEGER), you can simply do:

const { DataTypes } = require("Sequelize");

Foo.hasOne(Bar, {
  foreignKey: {
    // name: 'myFooId'
    type: D

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

https://github.com/dotnet/efcore/blob/9b66f4c1f865b2a897f2b6f0776c2e1a1a25f4ef/src/Microsoft.Data.Sqlite.Core/SqliteCommand.cs#L259

https://github.com/dotnet/efcore/blob/9b66f4c1f865b2a897f2b6f0776c2e1a1a25f4ef/src/Microsoft.Data.Sqlite.Core/SqliteCommand.cs#L310

They can be allocated once per SqliteConnection.

When I change ent field to have Default after the table was already created,
the migration doesn't change the column with command like:
ALTER TABLE users ALTER COLUMN name SET DEFAULT 'unknown';

• The issue is present in the latest release.
• I have searched the issues of this repository

Setup

Setup a project with sqlite using the following up.sql:

create table example (
    id integer not null primary key,
    calculated integer generated always as (id*2)
);

Versions

• Rust: 1.56.0 nightly
• Diesel: 1.4.7
• Database: Sqlite
• Operating System Linux

Feature Flags

• diesel: sqlite

Problem Description

Sqlite does

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

Is your feature request related to a problem? Please describe.
Now that the fields property is strongly typed, it seems like it would be a nice quality of life improvement to be able to infer what needs to be populated if the fields are specified for a query.

Describe the solution you'd like
Given the following code, the query should figure out that it needs to populate `['order.use