mariadb

Node: v12.22.12
Arch: x64
Platform: linux (QNAP TS-251)
Docker: true
Database: mysql2
ProjectOnRootDB: false
RootDB: mysql2
PackageVersion: 0.91.10
DataBase Version: MariaDB 10.5.8

Steps To Reproduce

1. In table "Arztadressen" set pictures of doctors
2. Create link from "Impfbuch Werner" to "Arztadressen"
3. Set column in table "Impfbuch Wern

https://github.com/sequelize/sequelize/blob/8a1429d6044123bba3a3f312b2e0c74b0c829990/lib/model.js#L1271

If I create any model with
charset: 'utf8mb4', collate: 'utf8mb4_general_ci'

sequelize translates it to this for mysql

CREATE TABLE IF NOT EXISTS tablename ... ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE utf8mb4_general_ci;

On stepping through the code, it seems that the issu

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

Issue description

This option will improve performance in many scenarios
https://dev.mysql.com/worklog/task/?id=8134

https://www.facebook.com/weixiang.zhai/posts/678596755543802

Is there an existing integration?

• I have searched the existing integrations.

Use Case

This will allow to host the software on a serverless and stateless service. This will facilitate scaling because no critical data will be on the disk of the system running the application.

Motivation

Allow users to save resources and money.

Implementation

No response

Anything e

While network maintenance was being performed the following error popped-up:

 thread 'main' panicked at 
'called `Option::unwrap()` on a `None` value': 
...../sqlx-core-0.5.13/src/postgres/listener.rs:165

Unfortunately I was unable to reproduce this issue in a lab environment. Looking at the code however, I would imagine the culprit is:
https://github.com/launchbadge/sqlx/blob/bd40c

Describe the bug

After updating to 5.2 I've noticed that phpMyAdmin stopped remembering how tables were sorted when navigating. I didn't find any other report about that so I'm guessing it's something related to my setup somehow. I tested this on two different setups and two different browsers. I don't get any errors in UI and in browser's console.
What can possibly produce this issue? Som

These files when added magically but not part of git tracked files causes update failure.

reference: frappe/bench#1225

related: frappe/frappe#16616 (you'll find which function create this file in this PR)

Environment

Liquibase Version: 4.6.1

Liquibase Integration & Version: 4.6.1

Liquibase Extension(s) & Version: 4.6.1

Database Vendor & Version: MySQL8.0.27

Operating System Type & Version: MacOS Monterey 12.0.1

Descript

QueryProc case is more tricky. It calls ExecuteReader[Async] and main issue here is that output parameters (at least for SQL Server, cannot tell about other providers right now, but probably the same) available only after all data consumed from reader. E.g. this is the reason why we generate ToList calls in scaffolded context for procedures with output parameters.

I don't see currently ho