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
Are the headlines we received correct? We started from the third line. Did we want to get its values as headers? Or would we like to get the values from the first row as headers? Or would we like to control this behavior through a parameter? Like :hdr :top-sheet-row || :top-range-row || :numeric-representation ;; or maybe even numeric, like we can do in excel itself
Here I’m almost sure that we are dealing with unexpected behavior, but I’ll still clarify whether this is so. Should we have gotten lines 1 and 2 in the example above? Or if the first line is line 3, then then we only deal with lines 3 and above? An exception is possible in the form of taking the value for the header from the first row in the sheet.
Is it really necessary to limit the :rows(Number of rows to extract) parameter to 10000 values? Maybe change it to 1048576 which represent maximum row count xlsx format supported? When I first encountered that I only got 10,000 records, it was unexpected for me.
If the :row parameter was specified, were :rows meant to be counted from :row or from the top row in the table?
The text was updated successfully, but these errors were encountered:
@velios looks like we have a bug. Please see responses below #2 if you specify :hdr and row 3 the expectation is that the table begins on row 3 and row 3 has the headers for the table. #3 agreed #4 horrible naming on my part but what i intended for row and rows should have been row-start and row-end respectively.
Let's look at the following example
This is data from example table without opts. Let's set start-row(row) to 3 and rename columns with data from the first row
Some questions about happen above?
:hdr :top-sheet-row || :top-range-row || :numeric-representation ;; or maybe even numeric, like we can do in excel itself
The text was updated successfully, but these errors were encountered: