Hi BaseX team,

 

Has the “header” option on csv:parse changed between BaseX version 11.6 and 11.7?

 

Here is an example to illustrate what looks like a problem or change. Given a tab separated text file such as this:

 

aaaa      bbbb     cccc

a1          b1          c1

a2          b2          c2

 

This query uses the “header”: “yes” option on csv:parse which should map column names to element names.

 

"tsv-test.tsv" => file:resolve-path() => file:read-text() =>

  csv:parse(map{'separator': 'tab', 'header': 'yes'})

 

BaseX version 11.6 produces the expected parse:

 

<csv>

  <record>

    <aaaa>a1</aaaa>

    <bbbb>b1</bbbb>

    <cccc>c1</cccc>

  </record>

  <record>

    <aaaa>a2</aaaa>

    <bbbb>b2</bbbb>

    <cccc>c2</cccc>

  </record>

</csv>

 

 

BaseX version 11.7 seems to be ignoring the header option and produces this output:

 

<csv>

  <record>

    <entry>aaaa</entry>

    <entry>bbbb</entry>

    <entry>cccc</entry>

  </record>

  <record>

    <entry>a1</entry>

    <entry>b1</entry>

    <entry>c1</entry>

  </record>

  <record>

    <entry>a2</entry>

    <entry>b2</entry>

    <entry>c2</entry>

  </record>

</csv>

 

If this is an expected change, is there any equivalent to the option “header”: “yes” ?

 

Best regards,

Vincent

 

______________________________________________

Vincent M. Lizzi

Head of Information Standards | Taylor & Francis Group

E-Mail: vincent.lizzi@taylorandfrancis.com

Web: www.tandfonline.com

Time zone: US Eastern

 

Taylor & Francis is a trading name of Informa UK Limited,

registered in England under no. 1072954

 

"Everything should be made as simple as possible, but not simpler."