<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Calc enhancement: ignore rows when importing CSV"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=138472#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Calc enhancement: ignore rows when importing CSV"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=138472">bug 138472</a>
from <span class="vcard"><a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> <span class="fn">V Stuart Foote</span></a>
</span></b>
<pre>(In reply to Heiko Tietze from <a href="show_bug.cgi?id=138472#c6">comment #6</a>)
<span class="quote">> ... since we have a dropdown "Column Type" where
> "Hide" is an option, we could easily add "Delete" to the list. This wouldn't
> affect the usability of the import dialog. But still, it's hard to imagine
> that users click through all columns for fine-tuning the import.
> ...</span >
No this would not be a columnar filtering. Here we are seeking to avoid parsing
*entire* rows from the sourced CSV--think of comments/meta data surrounding the
CSV.
If the row or "record" matches the search the entire row would be excluded from
the import, and not be parsed for columnar fielding.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>