You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The awaited result object still provides the rows and names properties (as well as other properties, currently status which is the protocol statement status such as "SELECT 1" indicating that one row was selected).
In addition, rows will now be typed such that we have row.get(name: keyof T) returning a value which matches the generic type parameter.
This issue was spawned from the discussions in #66.
The text was updated successfully, but these errors were encountered:
The initial API design was more or less compatible with https://node-postgres.com/, i.e.
pg
.In particular, query results were composed of rows and names (although the
pg
library provides fields from which you can get to the column names).We want to preserve this result interface, while also providing a more ergonomic and idiomatic interface which we will call the iterator interface:
The awaited result object still provides the
rows
andnames
properties (as well as other properties, currentlystatus
which is the protocol statement status such as "SELECT 1" indicating that one row was selected).In addition,
rows
will now be typed such that we haverow.get(name: keyof T)
returning a value which matches the generic type parameter.This issue was spawned from the discussions in #66.
The text was updated successfully, but these errors were encountered: