sql-server

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

Hi all. Congrats for the amazing software :)

Is your feature request related to a problem? Please describe.

It would be amazing to have the IN operator available in this drop-down list:

Describe the solution you'd like

Have the IN oper

It currently assumes that there is only a single ItemGroup with ArtifactReference items in it and that the ItemGroup doesn't have any other items in it. There are two issues with that :

1. If there are multiple ItemGroups with ArtifactReference items then we won't clean up until all items are removed
2. If the ItemGroup has other non-ArtifactReference items in it then those will be deleted

I currently need to connect to a Cloudera Impala instance in order to make queries and analyses.
It would be nice to be able to integrate this type of connection in DataStation.
I think it might require some sort of use of the Impala ODBC Connector / Driver.
Thanks!

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

I know it's not a course about RESTful principles but maybe you'll consider in the future extracting resource id from request body to path parameter ?

https://github.com/aspnetrun/run-aspnetcore-microservices/blob/c30712aa099bc335f5613a3b196ea1e943f800a5/src/Services/Catalog/Catalog.API/Controllers/CatalogController.cs#L85

https://docs.microsoft.com/en-us/windows/communitytoolkit/mvvm/migratingfrommvvmlight

Hey,

I see awesome MySQL preset but at case in my company there are still missing some features. We need three things:

• Run in root mode.
• Don't choose database at start because we have multiple db's in single MySQL instance.
• Mount Docker volumes. We use internal cache for seeds and it's saved in Docker volume.

Here's a quick sneak peek what I'm talking about in code:
https://g

We currently have support for some, but not all of MySQL's logical operators.

For example, select 1 OR 1; works, but not select 1 XOR 1;. We should review MySQL's logical operators and ensure we support all of them.

Found by: go-sqlsmith