diff options
| author | Stefan Majewsky <majewsky@gmx.net> | 2026-04-24 15:41:00 +0200 |
|---|---|---|
| committer | Stefan Majewsky <majewsky@gmx.net> | 2026-04-24 15:41:00 +0200 |
| commit | 027641ef9efec9ed5dfc463d9c2f38c32716d9b5 (patch) | |
| tree | f49025c72334b8e1c91cf1c4038ff7ae0e10ed11 /CHANGELOG.md | |
| parent | 9749eb317d39caa794cc27ef954656167cac487a (diff) | |
| download | go-oblast-027641ef9efec9ed5dfc463d9c2f38c32716d9b5.tar.gz | |
remove support for SQL dialects that rely on LastInsertId()
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.
Diffstat (limited to 'CHANGELOG.md')
| -rw-r--r-- | CHANGELOG.md | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/CHANGELOG.md b/CHANGELOG.md index e5e73eb..8d7c623 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -3,6 +3,17 @@ SPDX-FileCopyrightText: 2026 Stefan Majewsky <majewsky@gmx.net> SPDX-License-Identifier: Apache-2.0 --> +# v0.3.0 (TBD) + +Changes: + +- `Store.Insert()` now takes its arguments by-pointer. This is probably slightly less efficient, + but significantly safer because autogenerated field values cannot be disregarded by accident. +- Removed support for SQL dialects that rely on LastInsertId() for ID columns. + Using a RETURNING clause to collect autogenerated field values is objectively better in every way, + and has been supported by both MariaDB and SQLite for at least six years. + In practice, this only drops support specifically for Oracle MySQL. + # v0.2.0 (2026-04-18) Changes: |