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

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

See dotnet/EntityFramework.Docs#3207

It would be useful for ApplyConfigurationsFromAssembly to still use a parameterless constructor if there is one, even if it is not public.

Also, ApplyConfigurationsFromAssembly should warn if it finds a configuration that would be instantiated except that there is no parameterless constructor.

• I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡

index.Edges("myEdge").Fields("myField")

should generate a different index than

index.Fields("myField").Edges("myEdge")

Motivation 🔦

The order of columns on index is relevant.
Currently Edges columns

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")]

   

Hello,
I use postgres 12 with “MATERIALIZED” statement,
and I once asked on Discord how to use the “MATERIALIZED” statement in go-pg,
and get that is not support now.

Expected Behavior

WITH AS MATERIALIZED (...)

Is your feature request related to a problem? Please describe.
In trying to setup a new database from an initial migration I realized there's no way to create a new database from scratch. Is that accurate?

Describe the solution you'd like
Something akin to rake db:init or rake db:create where mikro-orm will take the runtime config and create a new database if it doesn't exist