mssql

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

Preflight Checklist

• I have completed all Troubleshooting Steps.
• I'm on the latest version of Directus.
• There's no other issue that already describes my problem.

Describe the Bug

If you ca

currently I'm unable to implement decode for My Type:

impl Decode<'_, Postgres> for MyType {
    fn decode(value: PgValueRef<'_>) -> Result<Self, BoxDynError> {
        // because this is private
        match value.format() {
            PgValueFormat::Binary => todo!(),
            PgValueFormat::Text => todo!(),
        }
    }
}

When creating a dump from OpenEdge (Progress) database, boolean fields will contain the following values:

• "yes" - true
• "no" - false
• "?" - null. I am assuming that everything else than yes/no is null here.

The problem faced currently?

While adding an ingress route, or a target in ingress route.
If by mistake white space gets added to the route or host. We get the error specified route not found or unable to reach the specified target

How can we solve it?

Mission control should remove the white space if present before saving the config

If you want this feature to be implemented, gi

I am trying to implement retry logic for Aws Aurora Mysql.

In Linq2db there is retyrpolicy already implemented except there is no way to pass retrypolicy to DataContext.
So I have extended the DataContext as follows.

public class RetryingDataContext : DataContext
{
protected IRetryPolicy _retryPolicy;
public RetryingDataContext(IDataProvider dataProvider, string c

Feature Request

A simple command that just pulls readable information from msdb..suspect_pages.

Problem to solve

At times you need to monitor the suspect pages a server may have or verify after you get logical errors returned from DBCC results, or even finding the dreaded 823/824 err

运行示例代码，如果把user对应的age和uid属性调换一下时，即使绑定了对应的tag，但是仍然按照数据库中顺序进行赋值，数据库的第一列uid对应的了user类的第一个属性age

PostgreSQL

Don't use serial

For new applications, identity columns should be used instead.