go-jet

Yeah, VALUES statement is not implemented yet. SELECT can be used for one row and SELECT with UNION ALL can be used for multiple rows. For instance: ```go input_rows :=...

Hi @wexder. Yeah, it makes sense to have a json literal.

Support added with v2.9.0 release.

`VALUES` is currently not supported. There is a workaround using [Raw](https://github.com/go-jet/jet/wiki/Expressions#raw-operator) operator: ```go .ON_DUPLICATE_KEY_UPDATE( Link.ID.SET(Link.ID.ADD(Int(11))), Link.Name.SET(StringExp(Raw("values(name)"))), ) ```

Yep, it will be added eventually.

`values` operator will likely not be supported as both MySQL and MariaDB plan to deprecate it. MySQL new approach is using insert [row alias](https://dev.mysql.com/doc/refman/8.0/en/insert-on-duplicate.html). Support for `mysql` insert row alias...

Hi @driverpt. `.DebugSql()` will return SQL without parameters.

`DebugSql` will return valid sql. You can see sample [here](https://github.com/go-jet/jet#lets-write-some-sql-queries-in-go) or in [tests](https://github.com/go-jet/jet/tree/master/tests/mysql). But, note that `DebugSql` is not intended to be used on the production, because of the possible...

How big are the queries? 1MB? You can also fork the repo and update [ArgumentPlaceholder](https://github.com/go-jet/jet/blob/c29f0afd2bbc8364d6f1d46be24d1e4decb39616/mysql/dialect.go#L26) function - `return ":var_" + strconv.Itoa(ord)`. Or maybe update the code so that this function...

I think it is the best, for you to fork the project and make necessary changes. Additional changes will probably be needed, because this data source is not supported currently.