Round 2 of cleaning up SpiTupleTable
#3
Draft
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.
This removes
SpiHeapTupleData
andSpiHeapTupleDataEntry
in favor of something that is hopefully less complex.We also change
SpiTupleTable
to kinda look like an Iterator rather than actually implementstd::iter::Iterator
. This is a breaking API change, but a good one. The changes are reflected in the test and example code diffs.SpiTupleTable
has also been split up into a privateInner
struct that manages access to the wrappedpg_sys::SPI_tuptable
instance, allowingSpiTupleTable
to manage its lifetime. This also allows us to clone the inner object and share the "current row number"Inner::current
across all theEntry
-ies.Doing so avoids the need for the old
SpiHeapTupleData
type entirely while allowing us toimpl Index for SpiTupleTable
, which accesses attributes (columns) by their name or ordinal at the current position of the SpiTupleTable.ping @workingjubilee for review