custom separator in CSV mode
Friday, 11 May 2012 · 4 messages · last reply 14 May 2012
FE
Fabrice Etanchaud11 May 2012 16:14 #
Dear all at BaseX,
first of all, thank you for your fantastic job,
BaseX changed my life !
Do you plan to let users set a custom separator when importing in CSV mode ?
(the comma, semicolon, or tab are too restrictive)
best regards
Fabrice ETANCHAUD
Senior Software Engineer
edital
Berkenlaan 1
B-1831 Brussels, Belgium
<skype:fabrice.etanchaud?call>+32 2 716 32 32 general
+32 2 716 32 20 fax
fetanchaud at edital.com
corsearch.com <http://www.corsearch.com/> | edital.com
<http://www.edital.com/>
<outbind://899-00000000E439C83B50BF17409D8C27B7AE0425AF07005AA868536216F 543BAB9422EAEA5338B00000011020900005AA868536216F543BAB9422EAEA5338B00000 13AA36B0000/cid:image001.gif at 01CC0F02.2C91B6C0>
Confidentiality Notice: This email and its attachments (if any) contain confidential information of the sender. The information is intended only for the use by the direct addressees of the original sender of this email. If you are not an intended recipient of the original sender (or responsible for delivering the message to such person), you are hereby notified that any review, disclosure, copying, distribution or the taking of any action in reliance of the contents of and attachments to this email is strictly prohibited. If you have received this email in error, please immediately notify the sender at the address shown herein and permanently delete any copies of this email (digital or paper) in your possession.
CG
Christian Grün13 May 2012 17:54 #
Hi Fabrice,
Quoted text · Fabrice Etanchaud · 2 lines
> first of all, thank you for your fantastic job, > BaseX changed my life !
Wow, that sounds like an important event ;)
Quoted text · Fabrice Etanchaud · 2 lines
> Do you plan to let users set a custom separator when importing in CSV mode > ? (the comma, semicolon, or tab are too restrictive)
Which separators characters would you like to have added? The reason for having defined fixed characters is that they are easier to specify via commands, but we could e.g. additionally allow numbers as input, which would then be interpreted as Unicode codepoints (32: space, etc.).
Christian
FE
Fabrice Etanchaud14 May 2012 09:42 #
Hi Christian,
Unicode codepoints would be fine,
Sometimes data providers adopt very strange data formats ...
Regards
Quoted text · Christian Grün · 14 lines
-----Original Message----- From: Christian Grün [mailto:christian.gruen at gmail.com] Sent: dimanche 13 mai 2012 17:55 To: Fabrice Etanchaud Cc: basex-talk at mailman.uni-konstanz.de Subject: Re: [basex-talk] custom separator in CSV mode Hi Fabrice, > first of all, thank you for your fantastic job, BaseX changed my life > ! Wow, that sounds like an important event ;) > Do you plan to let users set a custom separator when importing in CSV > mode ? (the comma, semicolon, or tab are too restrictive) Which separators characters would you like to have added? The reason for having defined fixed characters is that they are easier to specify via commands, but we could e.g. additionally allow numbers as input, which would then be interpreted as Unicode codepoints (32: space, etc.). Christian
CG
Christian Grün14 May 2012 18:48 #
Quoted text · Fabrice Etanchaud · 2 lines
> Unicode codepoints would be fine, > Sometimes data providers adopt very strange data formats ...
Done [1]; feel free to check out the latest snapshot [2].
Christian
[1] http://docs.basex.org/wiki/Parsers#CSV_Parser
[2] http://docs.basex.org/wiki/Releases
Written for BaseX 7.2. BaseX may have changed since: please check the current documentation.
⚡Generated with XQuery