| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
| |
Forgot this in 0.1.0. Without this, I cannot migrate existing Gorp users
because Gorp does not understand `db:",auto"`.
|
| |
|