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

Sometimes it is needed to store compressed data in the DB. Unfortunately not all the DBs have built-in compression and FUSE compressed FSes are not available for every OS. So it may make sense to store compressed binary blobs in the DB.

Unfortunately when one sees them in DBeaver he sees them compressed, but often they are needed uncompressed. So it'd be nice to have a feature to decompress the

Hello Philip!
I think there is an issue with this part of the code of rqlite (store/store.go).

func (s *Store) Database(leader bool) ([]byte, error) {
	if leader && s.raft.State() != raft.Leader {
		return nil, ErrNotLeader
	}
	// Ensure only one snapshot can take place at once, and block all queries.
	s.mu.Lock()
	defer s.mu.Unlock()

	f, err := ioutil.TempFile("", "rqlilte-snap-

Given that we support CURRENT_TIMESTAMP, the lack of CURRENT_DATE feels like an omission. While you can hack it with date(now), I keep finding myself wishing there was a direct way to reference this. Given that now means CURRENT_TIMESTAMP, I think there's precedent for today meaning CURRENT_DATE. This is supported by all backends we support (and is in the ISO standard I believe).

Originally posted by @dimitri in https://github.com/dimitri/pgloader/timeline

That's good thinking, and I think that's relevant for another PR. The PR introducing the statistics singleton should also take care of the following bits of refactoring of the code:

• the singleton is named “state” as I initially though I would update the global state of the migration to be able to know

It looks like there are hints at connecting directly with a socket path https://github.com/beekeeper-studio/beekeeper-studio/blob/9ff3131030057364f31f3034677fc0f6a9bd48b5/src/lib/connection-provider.js#L23

https://github.com/beekeeper-studio/beekeeper-studio/blob/2521b8c66721c7e634a006a992bad4e4f1f6153e/src/lib/db/server.js#L22

But there does not appear to be anything in the UI to indicate

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,