go-orm-benchmarks
go-orm-benchmarks copied to clipboard
Advanced benchmarks for +15 Go ORMs.
Bumps [github.com/gobuffalo/pop/v6](https://github.com/gobuffalo/pop) from 6.0.3 to 6.0.6. Release notes Sourced from github.com/gobuffalo/pop/v6's releases. v6.0.6 What's Changed updated genny version to hide warning by @sio4 in gobuffalo/pop#747 Full Changelog: https://github.com/gobuffalo/pop/compare/v6.0.5...v6.0.6 v6.0.5 What's...
Bumps [github.com/go-rel/rel](https://github.com/go-rel/rel) from 0.34.0 to 0.38.0. Release notes Sourced from github.com/go-rel/rel's releases. v0.38.0 Changelog 36bf6b0 Allow named structs to be embedded (#303) v0.37.0 Changelog 57e2c90 Add join assoc query builder...
Bumps [gorm.io/gorm](https://github.com/go-gorm/gorm) from 1.23.5 to 1.23.8. Commits 9fd73ae Revert "use callback to handle transaction" fe01e1b Fix Model with slice data 46bce17 test: pg array type (#5480) 5c4016d Merge pull request...
Bumps [gorm.io/driver/postgres](https://github.com/go-gorm/postgres) from 1.3.6 to 1.3.8. Commits 237572f fix: handle database type array (#115) c2cfceb feat: add postgres index , impl Migrator GetIndexes func (#113) 3806f45 Skip simple protocol when...
- [ ] https://github.com/Masterminds/squirrel - [ ] https://github.com/golobby/orm - [ ] https://github.com/mazrean/genorm - [ ] https://github.com/VinGarcia/ksql
Bumps xorm.io/xorm from 1.3.0 to 1.3.1. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a...
Current benchmark iplementation is fine but it may contains some potantial problems and bugs. To escape these problems, we should create new benchmark suite by using https://pkg.go.dev/testing#Benchmark
Fixes efectn/go-orm-benchmarks#5
It would be great to have benchmarks for MSSQL, MySql and SQLite3 too!
Since Insert doesn't check for created Id for raw and ent, the inserted model's id is `0` and hence the subsequence update doesn't affect any rows, and hence the code...