Issue Description

While using model.bulkCreate, as we pass the options, an object which contains transaction, it comes modified after the execution

What are you doing?

We have called bulk

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

I am intentionally making this issue specific but I assume it could be expanded to include much more of the API.

Problem

I do not have the entire Prisma Client API perfectly (let alone roughly) committed to memory.

When I go to use it to query for many results the operations tell me nothing about what and why they will do. I only have types to work with.

I don't want to open my br

5.1.0-rc1

Vertical alignment of the table names seems off.
Same for the sum values of rows, size and overhead. Font size of these seems off too.

The PgConnectOptions uri parser currently supports only 4 keys: "sslmode", "sslrootcert", "statement-cache-capacity", and "host"

The Postgres connection uri spec notes that there are many more,

Environment

Liquibase Version: 3.8.0, 4.1.1

Liquibase Integration & Version: CLI

Database Vendor & Version: Postgress

Operating System Type & Version: Linux

Description

The Liquibase CLI has the "validate" command to check is a changelog

What do you think about adding try_convert next to Sql.Convert function?