Surya Asriadie

yes, you are correct, rel currently doesn't implicitly handle array types (if you think this will be useful, please feel free to open a pr 😄 ). as an alternative,...

> update on this https://github.com/go-rel/rel/blob/master/adapter/sql/builder.go#L338 function right? But It's ok to change the adapter function? because I think mysql and sqlite doesn't support for array value cmiiw. yes correct, mysql...

Done, thank you! 🎉

Hi so far I don't have any plan to make automatic schema migration. The reason is our schema always evolving, and sometimes it's include manual data migration, so having a...

I'm closing this issue for now, if you think you need this feature, and want to propose an implementation for this, please let me know. thanks

Hi @lafriks, It might be a good to know the use case where auto schema migrations is very useful? so I can have a better consideration about this feature :)

> in my case it would be to prevent having to write the same schema multiple times (once in a Go struct and once in an SQL file), having it...

hmm, so I believe it's mainly useful only for development? In that case, I believe something like https://alembic.sqlalchemy.org/en/latest/autogenerate.html will brings more value, but this will be on separate project.

I see, as I understand, it's not a fully auto migration where we leave the engine to do the migration magic, but more like traditional version based migration. Developer have...

I haven't though that much, probably either of: - `t.BigInt("product_id", rel.References("products"))` (I think this is simpler and easy to extend) - `t.References("products")` - `t.BelongsTo("products")` and more [inspiration](https://api.rubyonrails.org/v6.0.3/classes/ActiveRecord/ConnectionAdapters/SchemaStatements.html#method-i-add_reference) I think there's...