Replies: 2 comments 3 replies
-
It is only used for returning multiple relations within an imperative script, which may also be undocumented (I can't remember). I will remind myself to document these when the next release comes. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I mention this because if the columns can change between instances, then my latest pull request is buggy. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Originally I thought NamedRows::next was a kind of a cursor structure, to avoid storing large results all at once in memory, but after taking a closer look, the chain stores all data together anyway.
The instance in
next
can also store its own columns. Is this for reporting results from multiple queries?Could the documentation explain when the user can expect
next
to be populated, and whether the next set of rows is actually independent from the first?Beta Was this translation helpful? Give feedback.
All reactions