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

Environment

Knex version: knex@0.21.12
Database + version:

Microsoft SQL Server 2019 (RTM-CU8) (KB4577194) - 15.0.4073.23 (X64)
Sep 23 2020 16:03:08
Copyright (C) 2019 Microsoft Corporation
Developer Edition (64-bit) on Linux (Ubuntu 18.04.5 LTS)
OS: Docker under macOS

For MSSql tag @smorey2.

Feature discussion / request

1. Explain what is your use case

It

Images whose meta.orientation >= 5 have the wrong width and height.

Directus version: 9.0.0-rc.44

Meta from source:

Describe the bug
Incremental refreshkey with updateWindow for pre-aggregation generates broken SQL for MSSQL

To Reproduce

Setting up an incremental update for a pre-aggregation like this (ignore bogus values):

 somePreaggregation: {
            type: `rollup`,
            measureReferences: [somecount],
            timeDimensionReference: timestamp,
            granularity

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

Is it supported at the moment to have 'serialize_as' and 'deserialize_as' on the single field in the sturcture as shown below?

#[derive(Identifiable, Queryable, PartialEq, Debug, Serialize, Deserialize, Insertable)]
#[table_name = "blah"]
pub struct Data {

    #[diesel(serialize_as = "SensitiveStringSerializer")]   
    #[diesel(deserialize_as = "SensitiveStringDeserializer")]

   

It happened to me I deleted a column that had a foreign key constraint and for someone not working with databases, I didn't know it is a nono. It resulted in having multiple foreign keys after I added a new one to replace it.

Maybe we could either prevent it or warn the user that the foreign key should be first removed on the dropped column? Or remove the constraint with the column? Also, why c

When launching the Create project from database dialog from the context menu of a database, the server and database dropdown are already populated, but sometimes the database dropdown is blank for a few second while waiting for the list of databases to load.

It would be nice if th