go-jet

Different developers use various naming templates for partitions, so there's no single universal solution to exclude partition tables from generation. You can [customize generator](https://github.com/go-jet/jet/wiki/Generator#generator-customization) to skip unwanted tables.

Yeah, it seems you're right. We could add generator flag to handle this use case.

If everything is exported, then everything becomes part of the public API, which limits maintainability. For instance if we need to refactor something which is often the case, we might...

> genTemplate functions for MySQL, SQLITE, and Postgres to call Generate genTemplate in ./cmd/jet/main.go ? > functions in import "github.com/go-jet/jet/v2/postgres" (example commits provided) `windowExpand` - is not an expression, just...

Thanks, looks good. To wrap it up, it would be good to have at least one test here - https://github.com/go-jet/jet/blob/master/tests/postgres/generator_test.go. No need to assert every model file content, just one...

> Thanks, looks good. > > To wrap it up, it would be good to have at least one test here - https://github.com/go-jet/jet/blob/master/tests/postgres/generator_test.go. No need to assert every model file...

Fixed with - https://github.com/go-jet/jet/pull/516.

Would this PR help: https://github.com/go-jet/jet/pull/443? You open db connection manually and then pass it to generator.

What you describe as expected behavior is not an SQL builder but an ORM. SQL builder tries to mimics the underling sql without hiding any query details. For instance: ```golang...

If you want to quote the SQL builder library, at least quote the real SQL builder library. For example, this is JOOQ for Java: ```java public Condition condition(HttpServletRequest request) {...