Commit 6956b67
Clarify fetchmany rejection message: "non-negative" instead of ">= 0"
The rejection message read awkwardly at the point it fires: the guard
only triggers when the caller passes a negative size, so "must be >= 0,
got -5" reads like a contradiction. "non-negative" describes the same
constraint but scans correctly in the rejection context.
Updated the sync and async cursors together and adjusted the existing
regex pin test.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>1 parent 284add0 commit 6956b67
File tree
3 files changed
+4
-4
lines changed- src/dqlitedbapi
- aio
- tests
3 files changed
+4
-4
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
199 | 199 | | |
200 | 200 | | |
201 | 201 | | |
202 | | - | |
| 202 | + | |
203 | 203 | | |
204 | 204 | | |
205 | 205 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
371 | 371 | | |
372 | 372 | | |
373 | 373 | | |
374 | | - | |
| 374 | + | |
375 | 375 | | |
376 | 376 | | |
377 | 377 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
113 | 113 | | |
114 | 114 | | |
115 | 115 | | |
116 | | - | |
| 116 | + | |
117 | 117 | | |
118 | 118 | | |
119 | 119 | | |
| |||
129 | 129 | | |
130 | 130 | | |
131 | 131 | | |
132 | | - | |
| 132 | + | |
133 | 133 | | |
134 | 134 | | |
135 | 135 | | |
| |||
0 commit comments