Commit 901fb11
Import _DescriptionTuple from the dbapi layer in the async adapter
The async adapter re-declared ``_DescriptionTuple`` alongside the
dbapi layer with a comment explaining the defensive duplication.
But dbapi is a hard dependency of sqlalchemy-dqlite, so there is
no import boundary to preserve — and the two aliases can only
drift by silent modification of one side. Import the tuple shape
from the dbapi layer instead and keep the outer
``Sequence[...]`` wrapper so the adapter's permissive passthrough
contract (accepting list or tuple outputs) is unchanged.
A new pinning test asserts the two aliases are identity-equal so a
future refactor reintroducing a local copy would fail loudly.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>1 parent 0423e4c commit 901fb11
2 files changed
Lines changed: 22 additions & 10 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
19 | 19 | | |
20 | 20 | | |
21 | 21 | | |
| 22 | + | |
22 | 23 | | |
23 | 24 | | |
24 | 25 | | |
| |||
28 | 29 | | |
29 | 30 | | |
30 | 31 | | |
31 | | - | |
32 | | - | |
33 | | - | |
34 | | - | |
35 | | - | |
36 | | - | |
37 | 32 | | |
38 | 33 | | |
39 | 34 | | |
40 | | - | |
41 | | - | |
42 | | - | |
43 | | - | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
44 | 40 | | |
45 | 41 | | |
46 | 42 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
0 commit comments