go-jet

There is no migration support, because there are already a tone of good database migration tools like [goose, go-migrate, etc...](https://github.com/avelino/awesome-go#database-schema-migration)

`NULLS_FIRST`/`NULLS_LAST` support added in [Release v2.11.0](https://github.com/go-jet/jet/releases/tag/v2.11.0).

`FETCH_FIRST`/`FETCH_LAST` `WITH TIES` support added in [Release v2.11.0](https://github.com/go-jet/jet/releases/tag/v2.11.0).

Hi @v-byte-cpu. `VALUES` is not supported currently. You can use this [workaround](https://github.com/go-jet/jet/issues/69#issuecomment-761809025) for now.

Hi @amanbolat, As I see it, the issue is that `postgres.String` adds a mandatory `::text` cast. And that's unfortunate because behind `postgres.String`, there can be any of the currently unsupported...

Aha, I see. In that case we can go with option 1. It should be a small change. We can add a new field into `TableSQLBuilderColumn` something like `TypeTemplate jet.ColumnExpression`...

Yeah, it makes sense. At the moment this behavior can be also achieved using generator customization([model example](https://github.com/go-jet/jet/blob/f2e4b8551c48b97d0cd2d3deff47dc1b2aa2f04e/tests/postgres/generator_template_test.go#L173), [sql builder example](https://github.com/go-jet/jet/blob/f2e4b8551c48b97d0cd2d3deff47dc1b2aa2f04e/tests/postgres/generator_template_test.go#L201)).

It turned out to be a small change. I've made a fix on [sqlite_gen_col](https://github.com/go-jet/jet/tree/sqlite_gen_col) branch.

Sqlite support for generated columns added in [Release v2.11.0](https://github.com/go-jet/jet/releases/tag/v2.11.0).

Hi @canuran Can you use [optimizer hints](https://github.com/go-jet/jet/wiki/SELECT#optimizer_hints-mysql-only) instead?