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.
From some research discovered
here
and in the Netezza ODBC documentation
here,
the Netezza ODBC driver, by default, has a 'Prefetch Count' setting,
defaulting to 256, that limits the # of rows that will return for a
resultset. It's unclear whether you can set this number to -1 or some
really large integer # (4 trillion or so) and if that would work (or try
to consume that much memory by pre-allocating?).
In any case, RODBC has a setting
believeNRows
, so we introduce asimilar (though IMO better named) keyword argument
ignore_driver_row_count
, which, when set totrue
, will force theresult handling code to iterate rows with no known length, which is the
setting we want when we're unable to pre-allocate full columns.