go-jet

You can use jet with [custom model types](https://github.com/go-jet/jet/wiki/Query-Result-Mapping-(QRM)#custom-model-types) as well. Also those db aliases will be ignored by jet QRM.

Hi @lbe , > I see a performance increase of 2.5 - 3 times Interesting. I've never managed to get much performance improvement from prepared statements. Although I mainly tested...

> I will create a project on GitHub that is similar to my application to demonstrate the performance differences. That would be great. Thanks.

> As I state in the readme, something is going bad wrong with update - horrendous performance and it gets worse as the number of records in the database increases....

> I will check out the prep-stmt branch. It will probably be next weekend before I can. Final version of prepared statement would be different, but you still can give...

Regarding the performance difference. I don't think your code is testing only differences without and with a prepared statement. A side note, but still important, is that both test cases...

I've deleted previous message about prepared statement branch, to avoid confusion. The prepared statement implementation can be found on `stmt-cache` branch. To use it, you'll just need to update database...

Hi @kiranmylam , the next release should be around October. In the meantime you can use `stmt-cache` branch. It is now in sync with master branch.

I've made a quick fix for this bug on `bug290` branch. Special characters are removed from go identifiers.

I've changed my mind on this one. There were couple of bugs opened before for similar invalid character issues. To prevent any additional bugs from opening, I've made a [change](https://github.com/go-jet/jet/commit/6b098b8e41fc8adc22418202019b1e2cb2441b58)...