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
+32 2 716 32 32 general
+32 2 716 32 20 fax
fetanchaud@edital.com
corsearch.com http://www.corsearch.com/ | edital.com http://www.edital.com/
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.
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
Hi Christian,
Unicode codepoints would be fine, Sometimes data providers adopt very strange data formats ...
Regards
-----Original Message----- From: Christian Grün [mailto:christian.gruen@gmail.com] Sent: dimanche 13 mai 2012 17:55 To: Fabrice Etanchaud Cc: basex-talk@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
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
basex-talk@mailman.uni-konstanz.de
-
Christian Grün -
Fabrice Etanchaud