go-jet

I guess we could add `_` after each table column named `TableName`, `SchemaName` or `Alias`. In the meantime, workaround would be to customize generator.

> I think the point I was getting at is that I think it should fail and detect a failure rather than generate code that doesn't compile. The only way...

> Since we have a finite set of reserved words, can't the generator fail if it finds a column name titled one of those values you listed above? It doesn't...

Thanks. Looks good. :+1:

Related comment - https://github.com/go-jet/jet/issues/355#issuecomment-2160308646.

With the release v2.12.0 users can now build custom expressions and operators using newly exposed `CustomExpression` and `Token` functions. ([wiki](https://github.com/go-jet/jet/wiki/FAQ#operators))

Yeah, it looks good. You can also make it a bit more SQL like: ```golang type filterExpand struct { agg Expression } func (f *filterExpand) WHERE(cond BoolExpression) Expression { return...

Hmm, not sure why I closed this issue. It is a valid missing feature.

Hi @Q00 , There are already couple of examples for multiple conditions. For instance on the main [Readme](https://github.com/go-jet/jet#lets-write-some-sql-queries-in-go) page, [faq example](https://github.com/go-jet/jet/wiki/FAQ#how-to-construct-dynamic-condition) and in [Expressions](https://github.com/go-jet/jet/wiki/Expressions). You can also search tests for...

> Right now the default for Jet is to let postgres arrays get generated into golang strings. You can override the generated types, but then you'd also have to implement...