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

Go 1.15 will introduce a new Validator interface, which may be implemented by Conn to allow drivers to signal if a connection is valid or if it should be discarded:

https://tip.golang.org/pkg/database/sql/driver/#Validator

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

The font size of the SQL query (when we open a table for example) seems to be smaller than before.
Almost unreadable.

The background of the Database structure (sidebar) is now white where the tables are (not sure if it was intentional)

![image](https://user-images.githubusercon

I'm using postgresql, sqlx="0.4.0-beta.1".
My struct is like:

#[derive(Serialize, Deserialize, Debug, PartialEq, FromRow)]
pub struct Struct1 {
    pub a1: i16,
    pub a2: String,
    pub a3: Option<String>,
    pub a4: Option<serde_json::Value>,
    pub a5: serde_json::Value,
    pub a6: Option<String>,
    pub a7: Option<serde_json::Value>,
    pub a8: Option<f32>,
    pub a9: 

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

Hi guys,

I have a small question regarding the way Linq2Db treats ambient transactions (TransactionScope).

In the example (see below), if the first query runs before an instance of transaction scope is created, then the ambient transaction will be ignored. However, if the first query runs after the transaction scope is created, then the transaction will be respected.

This behavior looks m