Re: [basex-talk] skipping empty cells when parsing CSV

> > Both [1] and [2] seem to work , > though on [2], node() still seems to be the slightly faster alternative > (when knowing that elements can only contain at least one non-whitespace > character, or are empty otherwise, as is the case with my data). Exactly: If you write your own queries and

Re: [basex-talk] skipping empty cells when parsing CSV

Hi Christian, Fun it is, two birds with one stone! Both [1] and [2] seem to work , though on [2], node() still seems to be the slightly faster alternative (when knowing that elements can only contain at least one non-whitespace character, or are empty otherwise, as is the case with my data).

Re: [basex-talk] skipping empty cells when parsing CSV

Hi Ron, The proposed option has been added to the latest snapshot [1,2]. In addition, we’ve optimized the evaluation of fn:normalize-space. If it’s applied on element nodes, it will internally be rewritten to a more efficient representation: E[normalize-space()] →

Re: [basex-talk] skipping empty cells when parsing CSV

Hi Christian, As always, many thanks for your lightning-speed help! The update command appears to be way out of my physical memory league, but I'm subscribed to the GitHub issue. Best, Ron On 20/04/2023 14:28, Christian Grün wrote: Hi Ron, I agree that would be helpful. I’ve added a

Re: [basex-talk] skipping empty cells when parsing CSV

Hi Ron, I agree that would be helpful. I’ve added a GitHub issue [1]. As you’ve already indicated, you can post-process your databases instances. I think the easiest query for that is: delete nodes db:get('db')//*[empty(node())] …followed by an optional db:optimize('db'). Best, Christian