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

Issue Type: Bug

When you have a long list of changes when doing a Schema Compare the list scrolls to the top after check/unchecking a file at the bottom.

1. Do a Schema Compare that produces changes longer than the UI can show in one screen.
2. Scroll down and uncheck a file.
3. The window will scroll to the top.
4. Get frustrated when you have to scroll down to uncheck another fil

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

The sql.JsonDocument ToString method uses json.Marshall. This returns a string without any extraneous whitespace. MySQL on the other hand uses whitespaces for legibility:

mysql> CREATE TABLE t1 (c1 JSON);

mysql> INSERT INTO t1 VALUES
     >     ('{"x": 17, "x": "red"}'),
     >     ('{"x": 17, "x": "red", "x": [3, 5, 7]}');

mysql> SELECT c1 FROM t1;
+------------------+
| c