go-oblast/query.go, branch v0.9.0

return a concrete type from Wrap() to enable non-Oblast DB operations

2026-05-12T23:13:17+00:00

Insert, Upsert, Update, Delete: do not panic on indirection through nil pointer

2026-05-12T22:40:24+00:00

clarify docstrings, put down TODOs based on review feedback

2026-05-12T11:25:00+00:00

change Handle to a generic interface without explicit dep on database/sql

2026-05-12T11:11:41+00:00

add ctx arguments to most methods

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

shave off some more allocations

2026-04-29T22:26:10+00:00

note to self: bad memory usage stats for Insert()

2026-04-24T14:17:41+00:00

add Store.Upsert()

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

remove support for SQL dialects that rely on LastInsertId()

2026-04-24T13:41:00+00:00

While researching for Upsert(), I noticed that both SQLite and MariaDB
support INSERT with RETURNING clause, which is objectively better than
LastInsertId() and cuts out a lot of useless crap from the codebase
(esp. from monomorphization-relevant methods).

The only tangible downside is that this drops support specifically for
MySQL, but you know what? Fuck Oracle.

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.