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

EF Core uses a class Migration, and if you add a new migration with name "Migration" it will break the build.

dotnet ef migrations add Migration

results with Circular base class dependency involving 'Migration' and 'Migration'

I recommend that "migrations add" adds a validation for this...

Include stack traces

Migrations/20201106105308_Migration.cs(6,26): error CS0146: Circul

Problem

There are some servers like fastify that allow to define json schemas in order to provide better performance and input / output data validation. Right now I am using prisma with fastify and have to manually define such schemas. Most of these, however, would

With #2571 merged diesel now officially supports GROUP BY causes. As mentioned in #210 we have no concrete planes for supporting HAVING clauses in the next release. I've opening this issue to just have one for HAVING clauses + write down some notes for potential contributors. So if anyone is interested in adding support for such clauses feel free to open a PR.

Steps to add support for `HA

I ran into this when trying to index the id field of all my schemas, which was derived from a base mixin.

I am getting entc/gen: invalid index for schema "User": unknown index field "id" for that field, even though I know it exists and so does the database.

I tested, and this is present when the id field is not provided (default), when it is explicitly defined in the schema, and when it

go-pg doesn't follow any fixed constraint name conventions.

type TestAccess struct {
	Id        string   `pg:"type:uuid,default:uuid_generate_v4()" json:"id"`
	BatchId   string   `pg:"type:uuid,on_delete:CASCADE,unique:batch_id_test_id" json:"batch_id,omitempty"`
	Batch     *Batch   `json:"batch,omitempty"`
	StudentId string   `pg:"type:uuid,on_delete:CASCADE" json:"student_id,omitempt

what is prefer way to add relation and remove relation? I found example as below, but I did't find any document about the two methods.

 case 'ADD_AUTHOR_TO_BOOK':
        Book.withId(action.payload.bookId).authors.add(action.payload.author);  // add new entity ,  add relation?  this doesn't work.
        break;
    case 'REMOVE_AUTHOR_FROM_BOOK':
        Book.withId(action.payload.bo