Surya Asriadie
Surya Asriadie
I see, hmm maybe let's go for panic now? and adds some comment on the alter function?
okay, then let's align with sqlite3
@lafriks is this ready to be merged?
> Should this be merged only when all related repo changed are done? I prefer this, after all merged, we can update `go.mod` on separate PRs to point to tagged...
could you give examples? and is the database type specific code will be in sql package?
got it, I think it's should be okay to add some metadata information like this I prefer `func Name() string`, and maybe have a constant (ex: `Name`) in each adapter...
@lafriks need to be updated too https://github.com/go-rel/reltest/blob/main/nop_adapter.go https://github.com/go-rel/mssql
probably we also need to provide exclude function?
maybe as pointer: - define a mutator, example: https://github.com/go-rel/rel/blob/master/on_conflict.go#L13 - register the mutator here: https://github.com/go-rel/rel/blob/master/mutation.go#L31 - use mutator here: https://github.com/go-rel/rel/blob/master/structset.go#L32 there's also map type: https://github.com/go-rel/rel/blob/master/map.go#L22
will adding the lock statement manually before create table solve your issue? example: ``` func MigrateCreateTodos(schema *rel.Schema) { schema.Do(func(ctx context.Context, repo rel.Repository) error { return repo.Exec(ctx, "LOCK TABLE pg_catalog.pg_namespace IN...