go-oblast, branch v0.5.0

v0.5.0

2026-05-08T14:58:04+00:00

allow both None or ErrNoRows in SelectOne{,Where}

2026-05-08T14:52:46+00:00

The None-returning style is more convenient when the application needs
to genuinely behave differently in this case, e.g. returning 404 from an
HTTP API endpoint (instead of 500 for a generic database error).

The ErrNoRows-returning style is more convenient when control flow is
not different for this case vs. other error cases.

v0.4.0

2026-05-04T14:23:38+00:00

return None instead of ErrNoRows from SelectOne{,Where}

2026-05-04T14:23:24+00:00

run tests when a PR is posted on GitHub

2026-05-03T19:01:00+00:00

README: adjust contribution notes, acknowledge the non-ORM-ness

2026-05-01T22:18:44+00:00

v0.3.0

2026-04-29T23:55:09+00:00

shave an allocation and memcpy from Select() and SelectWhere()

2026-04-29T23:37:48+00:00

fix benchmark calling the wrong test function

2026-04-29T23:19:20+00:00

I should have been suspicious of the Gorm/Gorp numbers matching exactly :)

benchmark: provide a handwritten N=1 implementation for InsertAndDelete

2026-04-29T23:09:48+00:00

As I had expected, this removes an unfair disadvantage for Oblast, which
had to maintain two differently-typed slices for Insert() and Delete().
This is not really a fair comparison since usually you would not be
doing both operations in one go.

For Gorp, this rewrite is neutral. But in a shocking twist, Gorm somehow
does _significantly_ worse with a specialized N=1 implementation:

```
BenchmarkInsertAndDelete/N=1/via_Gorm-24
before: 11508 B/op    157 allocs/op
after:  12840 B/op    172 allocs/op
```