This repository was archived by the owner on Aug 19, 2025. It is now read-only.
Fix fetch_val for raw queries in Postgres backend #131
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As of now,
fetch_val
does not work for raw queries in Postgres. Possibly related to the discussion in #101.This is a simple fix that will distinguish between
row[0]
androw['foo']
in the case of raw queries.in
core.py
:in
backends/postgres.py
:In this case, key is
0
, whiletuple(self.row.keys())
is('id',)
, which raisesValueError: tuple.index(x): x not in tuple