Bruno Meneguello

About the linter, I'm just adding the translations as fast as possible, I'll run `flake8` before open the PR. I noticed the large merge you did recently, I'll rebase accordingly...

@longqzh I added translation support and portuguese translation, it would be nice if you could check what is required to proper chinese internationalization.

@jyhelle NW is now ready for French!

I will try to update the PT translation today

This issue happens because the Migrator only checks if the constraint is present by the name, and not by its content: https://github.com/go-gorm/gorm/blob/418ee3fc1939d87a05bbb8ac6d7c7223e2c4571f/migrator/migrator.go#L166 Probably a method `MigrateConstraint` is necessary to check...

Sorry, two years ago I had the time, now I'm not involved anymore with this project.

#407 does that nativelly, please check. Nodes can behave as Clusters.

I have similar issues with transaction. I'm using sqlite for unit tests and have `SetMaxOpenConns(1)`. When I try to use gen.Transaction it locks, but gorm.DB.Transaction works.

The same happens to me, I have the following scenario: ```go func TestMissingCallToSetenv(t *testing.T) { ... { // Just a block for scoping t.Setenv("XXX", "YYY") ... } } ``` and...

@a-h the problem happens on code generation. The variable generated for required attributes uses the json attribute name [directly](https://github.com/a-h/generate/blob/96c14dfdfb601f0f624e776e44ced4aa3dadf8d9/output.go#L191) instead of converting to a safe go name using [getGolangName](https://github.com/a-h/generate/blob/96c14dfdfb601f0f624e776e44ced4aa3dadf8d9/generator.go#L328)