Joe, just in case it is of interest to you: the TopicTools framework,
downloadable at
https://github.com/hrennau/topictools
contains an XQuery-implemented, full-featured csv parser (module
_csvParser.xqm, 212 lines). Writing XQuery tools using the framework, the
parser is automatically added
@Hans-Jürgen… Nice work, thanks for the hint!
On Sun, Sep 11, 2016 at 10:23 PM, Hans-Juergen Rennau wrote:
> Joe, just in case it is of interest to you: the TopicTools framework,
> downloadable at
>
>https://github.com/hrennau/topictools
>
> contains an XQuery-implemented,
Hi Joe,
My concern is that a single regex, no matter how complex, won’t do
justice to parse arbitary CSV data. The CSV input we got so far for
testing was simply too diverse (I spent 10% of my time into
implementing a basic CSV parser in BaseX, and 90% into examining these
special cases, and
Joe, concerning your regex, I would complain, too! Already the first two
characters
(?render the expression invalid:(1) An unescaped ? is an occurrence
indicator, making the preceding entity optional(2) An unescaped ( is used for
grouping, it does not repesent anything
=> there is no
My surprise ended up with the finding that I introduced an error while
gradually preparing our code for (the long path to) query
precompilation. Thanks! It has been fixed [1].
Cheers
Christian (just the name, btw, not the confession ;)
[1] http://files.basex.org/releases/latest/
On Sun, Sep
Thanks for your replies and interest, Hans-Jürgen, Marc, Vincent, and Christian.
The other day, short of a comprehensive solution, I went in search of
a regex that would handle quoted values that contain commas that
shouldn't serve as delimiters. I found one that worked in eXist but
not in
Hans-Jürgen,
I figured as much. I wonder if we can come up with an xsd-compliant regex for
this purpose? It may not give us a full-featured CSV parser, but would handle
reasonably uniform cases.
Joe
Sent from my iPhone
On Sun, Sep 11, 2016 at 3:39 PM -0400, "Hans-Juergen Rennau"
Hans-Jürgen, wrote:
! Already the first
> two characters
> (?render the expression invalid:(1) An unescaped ? is an
> occurrence indicator, making the preceding entity optional(2) An
> unescaped ( is used for grouping, it does not repesent anything
> => there is no entity preceding the ?
Hi there,
Sorry, I lost track (but at least I’m back)… Does this also happen
with newer versions of BaseX, such as with the latest release or the
latest snapshot [1]?
Thanks in advance,
Christian
[1] http://files.basex.org/releases/latest/
On Wed, Aug 24, 2016 at 3:19 PM, Dirk Kirsten
Hi Genneva,
See [1] for more details on how to overwrite global options (such as
the database directory) in BaseX.
Best
Christian
[1] http://docs.basex.org/wiki/Options#DBPATH
On Thu, Sep 1, 2016 at 12:03 PM, Wang, Genneva wrote:
> Hi
>
> I’m trying to set up to having
Hi Joe,
Thanks for your mail. You are completely right, using an array would
be the natural choice with csv:parse. It’s mostly due to backward
compatibility that we didn’t update the function.
@All: I’m pretty sure that all of us would like having an EXPath spec
for parsing CSV data. We still
Hi Carl,
> I am wondering if you might have any suggestions on how to debug this and if
> you are logging any information in case a thread dies.
You could play around with trace() or prof:variables(), or activate
debugging via -d or SET DEBUG ON.
> We are running 8.5.2.
In BaseX 8.5.3, we
Hi Marco, thanks Vincent,
At first glance, I am surprised that file:base-uri() is required here,
basically because I would expect both variants to resolve to the same
directory. I will check it in more detail soon.
On Sat, Sep 3, 2016 at 11:18 AM, Marco Lettere wrote:
>
13 matches
Mail list logo