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

1. Exception Case:
LINQ: Here, I have a query which is doing a GroupJoin on an DbSet and then adding other inner joins.
Repository.ConvertToBigIntTable -> This is an output of a call to a Table-Valued function which returns an IQueryable (T is a Keyless entity having a long Id field)

private IQueryable<IDocumentTypePermission> GetDocumentTypePermissionsTest<T>(IQueryable

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

Diesel currently supports the postgres json and jsonb types. We do not provide built-in support for various operators available for these types. This is a tracking issue for adding support for these operators.

The general strategy for adding support for new operators is as following:

1. Define the operator via [`infix_operator!(

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

Describe the bug

Summary:

Strict typing for passing an array to orderBy argument does not work if the entity has a property length. Contents of the array are not type checked.

Long description:

I ran into this issue while updating some of my utility functions to also accept an orderBy argument typed as QueryOrderMap<T> | QueryOrderMap<T>[] just like in FindOptions:

htt