go-oblast/benchmark/benchmark_test.go, branch v0.4.0

return None instead of ErrNoRows from SelectOne{,Where}

2026-05-04T14:23:24+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
```

add ctx arguments to most methods

2026-04-29T22:56:38+00:00

benchmark: compare InsertAndDelete to plain SQLite using QueryRow for INSERT

2026-04-29T21:36:28+00:00

exclude testhelpers from coverage testing

2026-04-24T14:10:09+00:00

change Store.Insert() to take arguments by pointer

2026-04-19T12:25:13+00:00

This increases memory overhead slightly, but when converting Gorp uses
into Oblast, I saw that there is a legitimate risk of just ignoring the
result value and continuing with the unupdated records. So according to
the design priorities that I myself laid down, I'm sacrificing some
performance for safety of use.

add type PreparedSelectQuery

2026-04-18T15:10:34+00:00

write out a proper README

2026-04-18T14:24:52+00:00

benchmark: add Gorm

2026-04-17T20:46:28+00:00