aboutsummaryrefslogtreecommitdiff
path: root/query_test.go
Commit message (Collapse)AuthorAgeFilesLines
* Insert, Upsert, Update, Delete: do not panic on indirection through nil pointerStefan Majewsky2026-05-131-0/+73
|
* change Handle to a generic interface without explicit dep on database/sqlStefan Majewsky2026-05-121-10/+10
|
* add ctx arguments to most methodsStefan Majewsky2026-04-301-17/+27
|
* add Store.Upsert()Stefan Majewsky2026-04-241-2/+96
|
* exclude testhelpers from coverage testingStefan Majewsky2026-04-241-3/+3
|
* remove support for SQL dialects that rely on LastInsertId()Stefan Majewsky2026-04-241-164/+29
| | | | | | | | | | 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 pointerStefan Majewsky2026-04-191-27/+30
| | | | | | | | 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 StructTagKeyIsStefan Majewsky2026-04-181-2/+3
| | | | | Forgot this in 0.1.0. Without this, I cannot migrate existing Gorp users because Gorp does not understand `db:",auto"`.
* fix Store.Insert() failing on tables without auto columnsStefan Majewsky2026-04-181-0/+45
|
* more test coverage, forbid non-zero auto columns during Insert()Stefan Majewsky2026-04-181-5/+196
|
* add TODOs for the remaining things that I want for 1.0Stefan Majewsky2026-04-171-0/+2
|
* basic test coverage for Insert, Update, DeleteStefan Majewsky2026-04-171-0/+137