orm

Issue Description

What are you doing?

I am trying to strongly type my application using Typescript and Sequelize. I have noticed th

Bug description

When you run npx prisma init everything executes without problems but the .gitignore file is being overwritten with the following content mentioned in Issue #3400

How to reproduce

1. Create an empty npm project
2. Create and add some contents to .gitignore
3. Run npx prisma init
4. Open the .gitignore file and notice it was overwritten

Expected beha

we only translate overload that starts from the beginning. We could also translate the one that takes starting position, TSQL method has that overload also.

When I change ent field to have Default after the table was already created,
the migration doesn't change the column with command like:
ALTER TABLE users ALTER COLUMN name SET DEFAULT 'unknown';

• The issue is present in the latest release.
• I have searched the issues of this repository

Consider the following code (using AsChangeset instead / in addition to Insertable produces the same error message):

#[derive(Insertable)]
struct Foo {
        #[column_name = "type"]
        ty: String
}

This code is wrong because eventhough the table has a column called type, the auto-generated schema.rs file renames that to type_ to avoid using a keyword as an

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

方便定位问题