Hi
You can use the serialisation parameter with no indent option.
Marc
On July 14, 2015 8:13:09 PM CEST, meumapple wrote:
>Hi,
>
>When I use the file:write function, the whitespaces before an element
>are deleted (and also the initial whitespace of a string in an
>element). Th
It is only
hardening dev / debug, since I don't know how to trace using BAseX server
(fn:trace seems not to output anything using the basex server, maybe I
missed something here ?).
Cheers
2015-05-11 22:05 GMT+02:00 Christian Grün :
> Hi Jean-Marc,
>
> > I guess that it might be d
Hi,
I am struggling to use Basex sql module together with Basex Standalone. I
am getting the error : [bxerr:BXSQ0007] Could not initialize supplied
driver: 'com.mysql.jdbc.Driver'
The sql connection works finely while using the Basex server.
I guess that it might be due to the fact that I don't
t all."
Cheers,
--Marc
On Tue, Apr 21, 2015 at 4:53 PM, Christian Grün
wrote:
> Hi Marc,
>
> I remember this issue has been discussed before (I just cannot find
> any online reference).
>
> I agree that the produces annotation should be ignored if no Accept
> header is
]
http://exquery.github.io/exquery/exquery-restxq-specification/restxq-1.0-specification.html#produces-annotation
--Marc
Bummer, it's very tricky to isolate/repro in a minimal case.
At the moment don't have the time to pursue this further.
Maybe later.
--Marc
On Wed, Apr 8, 2015 at 2:27 PM, Marc van Grootel
wrote:
> Sure, I'm going to try this evening. If it's indeed Saxon we would
>
Sure, I'm going to try this evening. If it's indeed Saxon we would
probably need one anyways.
--Marc
On Wed, Apr 8, 2015 at 2:23 PM, Christian Grün
wrote:
> Hi Marc,
>
> I would tend to say it's a Saxon issue. We have no Saxon-specific code
> in our XSLT functions, a
de the grouping attribute.
...
Any idea if this is Saxon or BaseX issue?
--Marc
This is the top of the traceback.
Version: BaseX 8.1
Java: Oracle Corporation, 1.7.0_25
OS: Windows 7, amd64
Stack Trace:
java.lang.ArrayIndexOutOfBoundsExcepti
as ignored is quite handy to have.
--Marc
On Tue, Mar 31, 2015 at 8:16 AM, Lukas Kircher wrote:
> Hi Marc,
>
> sorry for the inconvenience - there have indeed been some changes to the
> unit module in the recent past, that are not yet covered by the
> documentation.
> I assume uni
eve %unit:ignore("message") is still supported.
--Marc
test summary overwriting the debugging info (such as
trace output).
Currently I then go to the command-line but it might be an idea to
somehow keep the output generated during test run visible.
Cheers,
--Marc
;> has xmldb:get-current-user and Marklogic has xdmp:get-current-user.
>
> We could add a function user:current() to the new User Module [1].
> More suggestions on other, possibly missing, functions are welcome.
>
> Best,
> Christian
>
> [1] http://docs.basex.org/wiki/User_Module
--
--Marc
valuates to false."
Haven't tested it for other conditionals.
--Marc
stand?
Marc
Le 18/03/2015 19:38, Leonard Wörteler a écrit :
Wrong mail account...
Weitergeleitete Nachricht
Betreff: Re: [basex-talk] How to process very long node sequences
Datum: Wed, 18 Mar 2015 19:26:00 +0100
Von: Leo Wörteler
An: Hans-Juergen Rennau
Kopie (CC): basex
ed to know intricate user details just need the handle on
the logged in / authenticated user (possibly from the servlet request
object?)
--Marc
dvisable anyway. But I don't know how your code looks so I
cannot say.
hth
--Marc
heck performance in your situation. In case you need to do many checks on
the same class attribute you may want to bind the tokenized value list with a
let instead of using this function.
I also remember that Michael Kay is looking into improving on exactly this use
case. But that doesn't h
Oh no I wouldn't.
--Marc
On Thu, Feb 19, 2015 at 12:04 PM, Christian Grün
wrote:
>> In gradle.properties I define system properties and then in a Gradle
>> build script I invoke a JavaExec task with the system properties.
>
> So, if I get it right, the repo path will be s
In gradle.properties I define system properties and then in a Gradle
build script I invoke a JavaExec task with the system properties.
task http(type: JavaExec) {
classpath configurations.basex
main = "org.basex.BaseXHTTP"
systemProperties System.getProperties()
}
--Ma
and try to come up with some repro steps.
--Marc
On Thu, Feb 19, 2015 at 11:24 AM, Christian Grün
wrote:
> Hi Marc,
>
>> I like to have the same workflow during development and take advantage
>> of having modules not depend on a fixed import path. When working with
>> the
ectory and affect server performance or even do nasty things.
--Marc
On Thu, Feb 19, 2015 at 11:08 AM, Christian Grün
wrote:
> Hi Maud,
>
> We are glad to hear that the DBA code serves as a good inspiration!
> After all, I think this should be its primary purpose. The way h
Hi Christian,
Yes indeed. This solves it. I removed the reference to the exist maven
repo from the build script.
Thanks,
--Marc
On Wed, Feb 18, 2015 at 9:30 AM, Christian Grün
wrote:
> Hi Marc,
>
> I'm working up last week's mails; here's finally some feedback ;)
>
re thing I noticed. When I sometimes get into a situation
where individual empty directories are also recognized as packages
(but I cannot delete them from the GUI package manager). With
repo:list() I then see something like this.
[1] https://github.com/theapsgroup/basex-gradle-starter
--Marc
I transferred the basex-gradle-starter repo to our organization. Old
links will keep working for a while but the official location will now
be:
https://github.com/theapsgroup/basex-gradle-starter
--Marc
On Fri, Feb 13, 2015 at 10:27 PM, Marc van Grootel
wrote:
> Hi,
>
> I've cr
I'm sending this again as my first try it didn't get picked up on the list.
--Marc
-- Forwarded message ------
From: Marc van Grootel
Date: Fri, Feb 13, 2015 at 12:00 PM
Subject: Re: [basex-talk] BaseX in maven
To: BaseX
Hi,
I have dealt with various ways to include
to go ;-)
Feedback welcome.
Cheers,
--Marc
On Sun, Jan 18, 2015 at 10:29 PM, Wendell Piez wrote:
> BaseX friends,
>
> If I run BaseX from Maven, do I always get to use the latest BaseX?
>
> Do I have to do anything special to set up BaseX in Maven to use
> SaxonHE instead of X
Christian,
Nice, thanks. Take care however, this C++ client has not been tested by
anyone except me ! I will add a readme.txt for reporting issues to BaseX
list.
2015-02-02 13:34 GMT+01:00 Christian Grün :
> Jean-Marc,
>
> Thanks for the new client! I have added your link to ou
than the makefile is outdated now. I did not install gcc on my
comp (always a pain to Mingw / gcc a windows installation ...), maybe Dirk
could have a look at it ?
Cheers, Jean-Marc
2015-01-31 17:55 GMT+01:00 jean-marc Mercier :
> Hi christian,
>
> I should probably update this old r
days left.
For information, I am toying with this client to switch from XQUERY to C++,
due to performance issues related to BaseX map and array computations. I
will try to report this problem, it might be a quite instructive and
interesting one.
2015-01-31 16:31 GMT+01:00 Christian Grün :
> Hi J
Hi all,
Just to report that I updated a C++ client for BaseX 8.0, according to the
new digest protocol (http://docs.basex.org/wiki/Clients)
Cheers
Yes, that makes sense. I forgot that I can just point to an app
specific catalog which then references the other catalogs that I need
and I can easily modify lookup by modifying this main app catalog.
Cheers,
--Marc
On Mon, Jan 26, 2015 at 2:06 PM, Marc van Grootel
wrote:
> No I didn'
No I didn't. But I will now ;-)
thanks
On Mon, Jan 26, 2015 at 1:57 PM, Fabrice Etanchaud
wrote:
> Hello Marc,
>
> Did you already take a look at the CATFILE property ?
>
> http://docs.basex.org/wiki/Catalog_Resolver
>
> Best regards,
> Fabrice
>
> -Messa
Sorry, for the no subject, lost it somewhere
On Mon, Jan 26, 2015 at 1:53 PM, Marc van Grootel
wrote:
> Hi,
>
> I'm trying to run validations on XML files that use DTD doctype
> declarations (DITA), I have a catalog.xml that contains the correct
> references for the e
k.
Or, maybe I could set some system property that forces the use of a
specific catalog (I hope to avoid using one fixed catalog though).
Ideas?
--Marc
Hi christian,
In this case it would be useless : it appears that the optimized query
consists in dumping this big map (about 400 000 000 integers), consisting
in several Giga octets of data when serialized.
2015-01-17 18:27 GMT+01:00 Christian Grün :
> Hi Jean-Marc,
>
> > No
$fun($args)};
prof:time(count(local:fun-profile(local:test#1, 1000))) : 843.18 ms
(with BaseX gui)
2015-01-17 17:00 GMT+01:00 Christian Grün :
> Hi Jean-Marc,
>
> This time, it was not that obvious to run your query (I stlil didn't
> find local:call). But my guess is that
})};
declare variable $test := prof:time(local:test(1000),false(),"2 :");
prof:time(count(local:test(1000)),false(),"1 :"),count($test)
Output :
2 :2508.42 ms
1 :710.51 ms
2015-01-17 13:27 GMT+01:00 jean-marc Mercier :
> Hello all,
>
> I wrote some basic de
Hello all,
I wrote some basic debugging / profiling tools for xquery code, using try{}
catch *{} mechanisms. However, profiling tools are not reliable.
The suspected reason is that inlining is not activated in try catch
expression. If confirmed, is it a desired behavior ?
Here is the basic test
- 1996.37 ms
Might it be garbage collector stuff ?
2015-01-14 8:18 GMT+01:00 jean-marc Mercier :
> Glory to our holy Leo for transmitting *brahmavidya* to shishya !!
>
> Turning back to this optimization problem, this might be trickier since
> execution time does not seem to behave l
)
prof:time(local:test1(7)) : 631.32 ms prof:time(local:test2(7)) : 451.32 ms
prof:time(local:test1(8)) : 2550.17 ms prof:time(local:test2(8)) : 507.32
ms
2015-01-13 22:43 GMT+01:00 Christian Grün :
> Hi Jean-Marc,
>
> beforehand: The first issue you reported back to us recently [1] h
-13 1:59 GMT+01:00 Christian Grün :
> Hi Jean-Marc,
>
> interesting one; it seems that $data is inlined and thus evaluated
> more than once. This doesn't happen if a FLWOR expression is used:
>
> let $data := fn:for-each ...
> for $n in 1 to $i
> return local:test
Hello,
I am facing some performances issues, probably due to unexpected query
reevaluation. Might it be due to the optimizer ? Here is a code to test
declare function local:test($i){
let $data := fn:for-each(1 to 1000, function($a){2*$a} )
(: let $data := xquery:eval("fn:for-each(1 t
Christian,
Excellent ! thanks a lot !
prof:time(local:savebin((1 to 1000),$binfile))
,prof:time(local:loadbin($binfile))
output is now
930.71 ms
907.04 ms
2015-01-08 22:11 GMT+01:00 Christian Grün :
> Hi Jean-Marc,
>
> > 2) However unserialization seems to perform awfully,
Christian,
Hi. Thx for the trick. It seems to work finely for serializing, but awfully
for unserializing :
1) Serialization using pack-integer is great. I am saving time and disk
space (around a factor 4).
2) However unserialization seems to perform awfully, or I do not know how
to do it properly.
Hello,
I am trying to insert big string into BaseX, and ended corrupting the whole
database. Here a test code , can you reproduce it ?
declare updating function local:dbtest($db as xs:string) {
db:replace($db,"map",{fn:serialize(1 to 1000)})
};
local:dbtest("MyDataBase")
output :
Impro
Hi Christian,
Thx a lot. Jean-Marc
2015-01-06 12:20 GMT+01:00 Christian Grün :
> Hi Jean-Marc,
>
> Dirk has already outlined well what this is about. I have added a new
> GitHub request [1].
>
> Cheers,
> Christian
>
> [1] https://github.com/BaseXdb/basex/issues/1052
Hi all,
I was trying to profile updating expression, and the result is
[XUST0001] prof:time(value[,cache[,label]]): no updating expression allowed.
Is this a desired behavior ?
Cheers,
Jean-Marc
Hello,
I am currently trying to store precomputed maps. The basic issue is to
store a sequence $seq of integers (that are indeed element id, i.e.
retrieved using db:node-pre).
Actually, I am storing it using
db:replace($db,"map",{fn:serialize($seq)})
and retrieve the sequence using using fn:token
Hello,
I was wondering if it is possible to improve template programming and
operator overloading with XQUERY 3.?
1) template programming : XQUERY provides a quite natural template
mechanism using type switch and instance:
declare function yell($animal) {
if ($animal instance of element()) then
errata : * declare variable $BigDb := db:open('MyBigDataBase');
2015-01-02 21:54 GMT+01:00 jean-marc Mercier :
> Dirk,
>
> Hello, sorry, but a very similar behavior seems to appear also in the
> latest version BaseX80-20141225.174535. Here is a new code to test :
>
jean-marc Mercier :
> Hi Dirk,
>
> You are right, I was using an old 8.0 BaseX version (seems to be the one
> from 23/09/2014). The problem does not appear in the latest release. Thank
> you !
>
>
> 2015-01-02 19:29 GMT+01:00 Dirk Kirsten :
>
>> Hello Jean-Marc,
>&g
Hi Dirk,
You are right, I was using an old 8.0 BaseX version (seems to be the one
from 23/09/2014). The problem does not appear in the latest release. Thank
you !
2015-01-02 19:29 GMT+01:00 Dirk Kirsten :
> Hello Jean-Marc,
>
> what version of BaseX did you use? I tried with t
Hello (and happy new year 2015 !)
I am facing some performance issues opening "big" databases due to an
(unexpected for me) argument evaluation during function composition. Is
this a normal behavior ?
Cheers
Here is a code description :
declare variable $db := db:open("MyBigDataBase");
declare
Hi,
Seems to work fine. At least, I didn't introduce any issues that
weren't already there. I didn't find the email address of the
maintainer I attach the file to this post. I have checked on recent
snapshot of 8.0 and 7.9.
If you want me to submit it differently or have me create a pull
request
Yesss. I think I have it. The salt and sha256 bit threw me off a bit
but after a look at the java code it was indeed trivial.
I do some more testing with it and also make it work with 7.x and
then I submit it to the maintainer.
Thanks for playing rubber duck.
--Marc
On Mon, Dec 29, 2014 at 5
ah, of course, I can always take a look at
https://github.com/BaseXdb/basex/blob/master/basex-examples/src/main/java/org/basex/examples/api/BaseXClient.java
I'll have another go at it then.
--Marc
On Mon, Dec 29, 2014 at 4:57 PM, Marc van Grootel
wrote:
> ... or maybe there's som
... or maybe there's some client code that is already updated, then I
could take a look at that.
--Marc
tle bit of guidance.
Sorry if I sound like a noob on this crypto stuff ;-)
[1]: http://docs.basex.org/wiki/Server_Protocol#Authentication
On Mon, Dec 29, 2014 at 2:54 PM, Marc van Grootel
wrote:
> Hi Andreas,
>
> Maybe that is a better way but I am using the client from within a
>
.
--Marc
On Mon, Dec 29, 2014 at 2:45 PM, Andreas Jung wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> I am working with Python and Base-X for a while but not through
> the standard Python bindings. Instead I am using the "pyfilesystem"
> modu
oding,
send_bytes_encoding)
129 # evaluate success flag
130 if not self.server_response_success():
--> 131 raise IOError('Access Denied.')
132
133 def execute(self, com):
IOError: Access Denied.
Thanks,
--Marc
o look for in the breakdown
between parsing/compiling/evaluating and printing.
Tips?
Thanks, and I hope you are all having a good Xmas break.
--Marc
/xquery-origami-3.html
Merry Christmas,
--Marc
[1] https://github.com/xokomola/origami
Verified, fixed.
Thanks
--Marc
On Sun, Dec 21, 2014 at 4:48 PM, Christian Grün
wrote:
> Hi Marc,
>
> Leo has just fixed my bug in the array iterator code. Thanks! A new
> snapshot is available.
>
> Christian
>
>
> On Sun, Dec 21, 2014 at 12:05 PM, Marc van Grootel
>
Hi,
I think I've spotted a bug in array:fold-left (using 20141219 snapshot)
array:tail([1,2,3]) => [2,3]
array:fold-left(
array:tail([1,2,3]),
(),
function($result, $fn) {
($result, $fn)
}
)
=> (1,2)
Using array:fold-right in the above example returns (2,3).
--
--Marc
Nnnnice, just in time for Xmas break.
Thanks.
--Marc
On Fri, Dec 19, 2014 at 1:54 AM, Christian Grün
wrote:
> Hi Marc,
>
> You are welcome to check out the latest snapshot [1,2,3].
>
> Have fun,
> Christian
>
> [2] http://files.basex.org/releases/latest
> [2]
Sounds really nice. I will definitely keep an eye on it (and watch the video)
--Marc
On Wed, Dec 10, 2014 at 3:04 PM, Andreas Jung wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi there,
>
> please allow me to announce a new toy project "XML-Director&
t;
> --
>
> [image: Afbeelding verwijderd door afzender.] <http://www.avast.com/>
>
> Dit e-mailbericht is gecontroleerd op virussen met Avast
> antivirussoftware.
> www.avast.com
>
>
>
>
>
>
> --
><http://www.avast.com/>
>
> Dit e-mailbericht is gecontroleerd op virussen met Avast
> antivirussoftware.
> www.avast.com
>
>
--
--Marc
Just in: Michael Kay gave fn:apply it's blessing and it will be in XQuery 3.1.
Great news.
Thanks to the WG and all who participated.
I don't want to sound too pushy, but ... eh ... when can we have it ;-))
See: https://www.w3.org/Bugs/Public/show_bug.cgi?id=26585
--Marc
But then again, I always like to see other templating implementations so feel
free to share your code.
Cheers,
--Marc
> On 28 nov. 2014, at 18:18, Maximilian Gärber wrote:
>
> Nice! Looks clean and compact.
>
> I could also think of an additional declarative layer that integr
not care which HTTP verb was used even a
totally invented one. Same arguments might apply for RESTXQ.
--Marc
On Mon, Dec 1, 2014 at 5:34 PM, Christian Grün
wrote:
> Maybe we could check out what's the JAX-RS way of doing this. So far,
> it has always been a good advice to do it the s
Hi Christian,
%rest:ANY would route all HTTP methods through that function.
Basically saying I don't care which method you call me with. So it has
nothing to do with the paths.
Hth
--Marc
On Mon, Dec 1, 2014 at 4:52 PM, Christian Grün
wrote:
> Hi Max, hi Marc,
>
> The %rest:path
, isn't it ...)
--Marc
d uptake. Often
as a base library on top of which other routing libraries/DSL's are
created fostering even more diverse approaches.
For the time being this will stay based on RESTXQ and stay away from
Java but it does feel clumsy and duplicating basic HTTP request
plumbing.
ah well.... we
It was already up for a while but DNS issues made my blog go missing
for almost a week. Now it's back.
http://xokomola.com/2014/11/18/xquery-origami-2.html
The post describes how to do screen scraping using Origami extractors.
I'm quite happy with the outcome.
--Marc
e not complete.
I'll be working on this library over the next month to get it into a
more usable shape.
Happy to receive comments and improvements.
--Marc
Stop the press .
No, really. I probably have to stop now. I was switching BaseX
versions and used a version where I didn't add Saxon yet. The HTMl
stylesheet I used didn't use any XSLT 2 features.
Face palm. Sorry for wasting your time
Can I get Google to forget this ;-)
--Marc
: 'Cannot find class '1.0'.'
FATAL ERROR: 'Could not compile stylesheet'
On Sun, Nov 23, 2014 at 10:40 PM, Marc van Grootel
wrote:
> Hi,
>
> I was using an XSLT 2 stylesheet to transform xqdoc XML to Markdown. I
> already had a stylesheet that did the
ROR: 'Invalid conversion from
'com.sun.org.apache.xalan.internal.xsltc.dom.AdaptiveResultTreeImpl'
to 'node-set'.'
So something is causing a fallback to Xalan XSLT 1 processor but I
cannot undersand why. However, if I remove all functions and named
templates this same stylesheet is compiled and executed fine using
Saxon again!!??
If necessary I can add some more code.
--Marc
lcome to the cutting edge
;-)
Happy to receive comments and improvements.
--Marc
Hi Christian,
Duh, you're right. I didn't start the new basexgui after I replaced
with your latest snapshot. command-line used the newer snapshot,
basexgui still the old one.
--Marc
On Sun, Nov 16, 2014 at 5:05 PM, Christian Grün
wrote:
> Hi Marc,
>
> This is what I g
... here are the trace messages
- X: ul
- FN: function($node_17 as node()*) as node()* { ((: node()*, true :)
xquery:eval("ul", { "":$node_17 })) }
- X: li
- FN: function($node_17 as node()*) as node()* { ((: node()*, true :)
xquery:eval("ul", { "":$node_17 })) }
--Marc
ing)
{
function($node as node()*) as node()* {
xquery:eval($selector, map { '': $node })
}
};
local:select(('ul','li'))(item)
--Marc
Verified fixed. Thanks. Didn't expect a fix on Sunday though ;-)
--Marc
On Sun, Nov 16, 2014 at 1:57 PM, Christian Grün
wrote:
> Thanks, Marc. A new snapshot is online.
> Christian
>
>
> On Sun, Nov 16, 2014 at 12:56 PM, Marc van Grootel
> wrote:
>> ... even we
... even weirder, it returns li/@id=last three times
--Marc
On Sun, Nov 16, 2014 at 12:51 PM, Marc van Grootel
wrote:
> Hi,
>
> I think I bumped into a bug (on 8.0 snapshot)
>
> let $input :=
>
> item 1
> item 2
> item 3
>
&
r; the nodes are returned in document
order with duplicates eliminated."
[1] http://www.w3.org/TR/xpath-functions-30/#func-outermost
--Marc
Thanks Marco and Andy.
I will go with XPath selectors and eval for now. John Snelson's
library is indeed interesting and a while ago I tried the parser part
for parsing XQuery into XML. I don't either understand it fully but it
seems to do it's job.
--Marc
Hi Andy,
I've looked at it before. Seems like a huge machine for the job. I
thought somewhere I read that performance on xquery:eval is really
good and my very simplistic toy example did seem to perform quite well
but I will need to do more experimenting.
--Marc
ing xquery:eval with XPath
string-selectors. How is the performance? Other downsides (such as
being non-standard)?
Thanks
--Marc
[1] https://github.com/xokomola/origami
Blog post is up on http://xokomola.com/2014/11/10/xquery-origami-1.html
It provides a bit more info on the design. But README on github is
also updated to contain more documentation.
Feedback welcome of course.
On Mon, Nov 10, 2014 at 12:05 PM, Christian Grün
wrote:
> Hi Marc,
>
> tha
ble to other
databases that support XQuery 3.0.
Happy to receive comments and improvements.
In an upcoming blog post I will provide some more info.
--Marc
mini-language, too often have to look up the syntax again.
A suggestion (especially when working with the somewhat weaker
glob-patterns) is to allow a space or semi-colon separated list of
glob-patterns and instead of select= use include= and exclude= -
similar to Ant's filesets.
--Marc
O
e set.
{
"meta": {
"export-date": "27-10-2014",
},
"base": "file:///F:/home/marcg/work/projects/website/_from_cms/locale/EN/xml",
"selectors": {
"includes": "*.xml",
"excludes": ()
},
&q
I will keep the 'fix' in a wrapper function then. Personally I
don't see the rationale for this in the spec.
--Marc
On Tue, Oct 28, 2014 at 3:03 PM, Christian Grün
wrote:
> Hi Marc,
>
> this behavior is compliant with the current spec [1]: The
> file:resolve-path function i
to use string-join($parts,'/') and having
slash at the end of URL's and filesystem paths doesn't feel right so I
always strip them off.
Hope I didn't sound too grumpy ;-)
Opinions?
Guess, changing it would trip up a lot of existing path handling code.
--Marc
my client data, thus containing confidential informations.
Don't you have another idea to go ahead with this issue ? If not, I'll have
to build a database from public data, like a wikipedia dump, but it will
take some time.
Cheers
2014-10-06 13:53 GMT+02:00 Christian Grün :
> Hi Je
rue
XMLPLAN: false
>
2014-09-27 11:34 GMT+02:00 jean-marc Mercier :
> Dirk,
>
> Hello !
> Sorry, the problem seems to be on BaseX side.
>
> 1- I have tried to use eclipse IDE setting the interpreter as a client.
> Doesn't work, it saturated my Java machine.
> 2- I have tr
ated my JAVA
Machine.
Do we have any way to check if a query run in verbose mode ?
Cheeres,
Jean-Marc
2014-09-26 16:20 GMT+02:00 jean-marc Mercier :
> Hi Dirk,
>
> Ok, thanks for the trick, that should work. The only point is that it
> should be less user friendly for devel
Hi Dirk,
Ok, thanks for the trick, that should work. The only point is that it
should be less user friendly for developing than using the eclipse IDE,
since I will have to set up the BaseX repo first of running a query.
2014-09-26 12:11 GMT+02:00 Dirk Kirsten :
> Hi Jean-Marc,
>
> I
Hi Dirk,
Thanks for your answer. I am setting up eclipse indigo, following the
step-up procedure http://docs.basex.org/wiki/Integrating_Eclipse. The only
difference is that I set using -Xmx12G as Interpreter Arguments.
Cheers
2014-09-26 11:44 GMT+02:00 Dirk Kirsten :
> Hello Jean-Marc,
&g
Hi all,
I am using BaseX' inspect:xqdoc module to generate xquery docs. I was
wondering how generating html pages for accessing this documentation from
the web, as for instance Leo did for
http://www.woerteler.de/xquery/modules/base64 ??
Thanx
cheers,
Jean-Marc
101 - 200 of 324 matches
Mail list logo
