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 behaviour should probably be the same in the following cases:
Straight read requesting a column that does not exist, or date range outside that covered by the symbol's index
QueryBuilder processing that depend on a column, or date range in the case of resampling or a date_range clause followed by other processing steps.
As it stands:
Straight read requesting a column that does not exist returns an empty dataframe with no rows or columns
Straight read requesting a date range outside the symbol's index returns an empty dataframe with no rows, and only columns specified to be included
QueryBuilder behaviour depends on whether the supplied queries can be combined with column selection, and whether the columns argument to read has also been provided
The text was updated successfully, but these errors were encountered:
alexowens90
changed the title
Rationalise behaviour when a column is requested that does not exist
Rationalise behaviour when a column or date range is requested that does not exist
May 9, 2024
The behaviour should probably be the same in the following cases:
QueryBuilder
processing that depend on a column, or date range in the case of resampling or adate_range
clause followed by other processing steps.As it stands:
QueryBuilder
behaviour depends on whether the supplied queries can be combined with column selection, and whether thecolumns
argument to read has also been providedThe text was updated successfully, but these errors were encountered: