> NOTE: When I look at the file in BaseX GUI, I see the .xsd file renamed as
> lower caps, but when accessing the DB though XML Oxygen/WebDAV connection, I
> see that the file has not really been renamed Anyhow, it might have a link
> with the reference not being resolved properly (?).
I have uplo
> So if you are using multipart/form-data in your request you might one to
> give it a try. Data will be put into a map and can be accessed this way.
> See the following snippet for an example (which I shamelessly stole from
> Christian, so kudos to him) [...]
Thanks Dirk, no reason to be shamed…
Hei Arto,
your proposal sounds reasonable. I have fixed our json serializer;
namespace declarations will now be ignored.
Hope this helps,
Christian
___
2013/7/24 Arto Viitanen :
> Is there any way to make json module (mainly json:serialize) handle
> namespaces? I tried fo
Hi Andrew,
just a quick answer: as you already proposed, the cleanest approach to
ensure sound database copies is to use the CREATE BACKUP (or COPY)
command, and transfer the resulting files to a second server instance.
Both commands should be sent to the database server in order to avoid
concurre
Hi Simon,
not sure if that helps, but you can try to deactivate whitespace
chopping in the prolog of your XQuery expression:
declare option db:chop "no";
...
Best,
Christian
___
2013/7/26 Simon Görke :
> Hi,
>
> I have small issue regarding the xslt:transform functio
lt-processor (instead of saxon) but resulted in the same
> problem.
>
> Any ideas welcome...
>
> Greets,
> Simon
>
>
>
> -Ursprüngliche Nachricht-
> Von: Christian Grün [mailto:christian.gr...@gmail.com]
> Gesendet: Freitag, 26. Juli 2013 14:56
> An:
g flag caused frequent problems in the
past. Due to legacy and storage issues, we are still hesitant to
simply change the default, but we are working on it.
Best,
Christian
[1] http://docs.basex.org/wiki/Options
> -Ursprüngliche Nachricht-
> Von: Christian Grün [mailto:christian.gr.
Dear Nesh,
sorry for letting you wait.
As BaseX has been optimized for database operations, it may not be the
best choice for streaming data. If creating a database is no
reasonable option, you could check out the commercial version of Saxon
[1] or have a look at Zorba’s XML Module [2].
Hope thi
t;
>
>
>
>
> it always returns " Syntax: <...>".
>
> Executing the same without CHOP=false in .basex works like a charm.
>
> Is there any chance this could be fixed?
>
> Best,
> Simon
>
>
>
>
>
> -Ursprüngliche Nach
(we have
> to get it running using 7.6), but I will come back to it when 7.7 is
> actually released.
>
> Thanks a lot for your help!
>
> Simon
>
>
> -Ursprüngliche Nachricht-
> Von: Christian Grün [mailto:christian.gr...@gmail.com]
> Gesendet: Mittwoch, 31. Jul
Hi Andreas,
as your scenario is quite a usual one, it’s difficult to guess what
may be the problem. Have you tried to use BaseX with the default
options (e. g., using no SERVERHOST option, etc.)? Did you check your
Firewall settings, did you try port 8080? Is there a particular reason
for using a
ot; command ever
> turned into an xquery function?
> Don't seem to see an equivalent in http://docs.basex.org/wiki/Index_Module
> thanks
> *P
>
> On 10/29/10 9:10 AM, Christian Grün wrote:
>> Hi Pascal,
>>
>> you might also use the (undocumented) database comman
ke this connection?
>
> best regards
> Andreas
>
>
>
> On 7/31/2013 5:59 PM, Christian Grün wrote:
>>
>> Hi Andreas,
>>
>> as your scenario is quite a usual one, it’s difficult to guess what
>> may be the problem. Have you tried to use BaseX with th
ata in the 7.6 version?
>
> best regards
> Andreas
>
> On 8/1/2013 11:06 AM, Christian Grün wrote:
>
>> Hi Andreas,
>>
>> thanks for the response. I haven't changed any ports. These are the
>>> default
>>> ports.
>>>
>>
>&
Hi James,
by default, all string results are XML-encoded. You’ll get the
expected result by declaring "text" as output option in the prolog
(header) of your query:
declare option output:method 'text';
let $someItem := ...
Our Wiki page on serialization may give you more hints [1].
Hope this
Subject 10
text/html
{fn:serialize({ $someItem })}
document
___
2013/8/2 Christian Grün :
> Hi James,
>
> by default, all string results are XML-encoded. You’ll get the
> expected result by declaring "text" as output option in the p
Hi James,
could you please have another look at your example and provide us with
some code that runs out of the box?
Thanks in advance,
Christian
___
2013/8/2 James Wright :
> Hey Christian,
>
> Thank definitely did the trick however it affects the entire query. The
> que
I have attached a possible solution; don’t hesitate to tell us if you
expect a different solution.
Best,
Christian
___
declare option output:method 'json';
let $htmlContent := Issue:
return
Test Subject 10
text/html
{ fn:serialize($htmlContent) }
Hi James,
it may be worthwhile to point out what serialization means in the context
of XQuery:
- on the one hand, we have the internal representation of XQuery values, in
which special characters like angle brackets are stored as single
characters.
- if we want to output results as text, all val
Dear Jörg,
have you tried BaseX 7.7 Beta [1]? The official release will be
available in a few days.
Best,
Christian
[1] http://files.basex.org/releases/latest/
___
2013/8/6 Jörg Beisiegel :
> Hello,
>
> unfortunately I do not get the archive:update function to work… I am
Hi Christoph,
two little observations that might help you to improve your queries:
> new ClientQuery(xQueryUpdate, SESSION,
> SESSION.getOutputStream()).close();
You need to execute your query, otherwise, this will be a no-op operation:
ClientQuery cq = SESSION.query(xQueryUpdate
Hi Jörg,
your query should work if you use the "archive:" prefix for your entry element:
let $updated := archive:update($archive,
{$doc}, $entry)
If you don’t specify on any options, you can also omit the element:
let $updated := archive:update($archive, $doc, $entry)
Hope this helps,
Christ
Hi Ertan,
> is there any possible problems to access database at same
> time by different process/threads ? What happens when trying to access a
> database that is already open by another BaseX instance ?
it’s no problem to access the same BaseX database by different
instances, as long as no upda
Hi Christian,
I’m not aware of such an abstraction layer, but I could imagine it may
be difficult to provide such a layer which is flexible and fast at the
same time, because eXist-db and BaseX work quite differently when it
comes to full-text processing. For example, BaseX provides various
featur
Hi everyone,
we are excited to give you Version 7.7 of BaseX -- the Happy-Birthday-Leo
Edition -- which provides a bunch of new and improved features:
XQUERY
- Support for XQuery 3.0 has been finalized
http://docs.basex.org/wiki/XQuery_3.0
- the Unit Module allows standardized testing of XQ
What about simply using XQuery?…
analyze-string('test MM23423 junk MM1 junkagain man', 'MM')
___
> I am trying to use analyze-string. I have this query:
>
> declare namespace str = 'str.analysis';
> declare function str:analyze-string($string as xs:string, $regex as
Dimitre,
thanks for the bug fix, for which I’ve created an entry in our bug tracker [1].
Best,
Christian
[1] https://github.com/BaseXdb/basex/issues/744
___
2013/8/11 Dimitre Novatchev :
> Hi,
>
> Given this XML document (in file example.xml):
>
> http://example.com/one"
Hi Wendell,
> for $record at $p in $recordSet
> where ($p ge $start) and ($p ge $end)
> return $record/process-record(.)
I would usually write this as:
$recordSet[position() = $start to $end]/process-record(.)
…but as the query optimizer rewrites some of the possible alternatives
to the same
Hi France,
it would be interesting to hear if the problem persists with BaseX
7.7. If yes, do you think it’s possible to build a little example that
allows us to reproduce the problem?
Thanks,
Christian
___
2013/8/14 France Baril :
> Hi,
>
> Setup: http server 7.6. Path t
Hi Marcel,
the XPath grammar allows spaces after slashes, which is why your query
is interpreted as..
... into /else ...
You can avoid this by using additional parentheses:
if(true()) then (insert node into /) else ()
Hope this helps,
Christian
___
2013/8/15 Mar
Hi Thomas,
> After migration to BaseX77, db:optimize is running into an exception:
> java.io.IOException: Stopped at ., 8/20:
> [java] [FOUP0002] Database 'xxx' is currently opened by another process.
> Before migration, I used BaseX761-20130303.204518, and this version worked
> well.
I guess yo
Hi Srini,
thanks for your report. I could reproduce the bug, even with the
standalone version of BaseX. The issue is related to our buggy locking
downgrades, which we reactivated some weeks ago (too early, as it
seems). I have added a GitHub issue [1] to track down the behavior,
and I have uploade
Hi Gerald,
have you been defining your commands in a BaseX command script? In
that case, you’ll now have to specify your queries in a single line or
(better) use the XML syntax for multi-line queries, which could e.g.
read as follows:
Hope this helps,
Christian
___
2013
Hi France,
my assumption is that, when a document is stored in the database,
non-breakable spaces are replaced with the equivalent Unicode
characters, which cannot be distinguished from simple spaces in the
editor (" " vs. " ". The reason is that all entities are normalized
and resolved before the
Hi Alexander,
I guess you are working with Linux. "ulimit -n" can be used to
increase the maximum number of opened files.
Best,
Christian
___
2013/8/28 Alexander Shpack :
> Hello!
>
>
> for $i in (1 to 1000)
> let $name := 'user_' || $i
> return
> (
> db:create( $na
Hi John, thanks Dirk,
> for $dbname in ('physicsSD', 'physicsLD')
> for $x in doc($dbname)//Doc[SD/Info/
> text() contains text {"emf waves"} all words or
> LD/Info/Para/text() contains text {"emf waves"} all words]
due to the dynamic choice of addressed databases, the full-text index
will not
Hi Graydon,
the BaseX command-line interface provides numerous command-line
options, but the GUI interface is limited to file arguments. Please
check out our documentation on start up options for more details [1].
Best,
Christian
[1] http://docs.basex.org/wiki/Startup_Options
___
Hi Victor,
as you already observed, the file size of all XML documents stored in
the database is 0 bytes. The reason is that the files are not stored
in their binary representation, but in an encoded representation,
which is faster for querying. The drawback is that this representation
does not en
ike to give it a try. ¿Anyone knows the trick?
>
> Regards,
>
> Víctor
>
>
>
> El 2013-09-05 17:43, Christian Grün escribió:
>
> Hi Victor,
>
> as you already observed, the file size of all XML documents stored in
> the database is 0 bytes. The reason is tha
Hi Richard,
thanks for your mail. Did I get you right that saving the result in
the GUI worked with 7.5, but stopped working with the latest version?
I tried to reproduce the problem, but I wasn’t successful so far. Do
you think you could provide us with a sample query that allows us to
reproduce
Hi James,
this looks like a potential bug, but it might be tricky to reproduce
it with sample data. Have you experienced similar feedback when using
Java?
Best,
Christian
___
2013/9/9 James Ball :
> Hello,
>
> I've got a collection with about 1.4 million small XML files i
The problem may be fixed now; could you please have a look at the
latest stable snapshot [1] and check out if it does what you expect?
Thanks in advance,
Christian
[1] http://files.basex.org/releases/latest
___
2013/9/9 Christian Grün :
> Hi Richard,
>
> thanks
Hi France,
by default, no ~webdav database exists; it is created as soon as a
file is opened in oXygen via WebDAV. The problem should be fixed if
you restart BaseX, oXygen, or both applications.
Hope this helps,
Christian
___
2013/9/11 France Baril :
> Hi,
>
> I deleted t
Hi Dimitre,
the bug you encountered has now been fixed [1]; feel free to check out
the latest stable snapshot [2] (7.7.1 will be released soon).
Best,
Christian
[1] https://github.com/BaseXdb/basex/issues/744
[2] files.basex.org/releases/latest
___
2013/8/11 Dimitre Nov
Dear all,
you are invited to check out our minor 7.7.1 release, which contains
the following patches and fixes:
XQUERY
• we have switched to the new map syntax (example: {'key':'value'})
• tail call optimization is now also applied to dynamic functions
• fn:subsequence() calls and sequence casts
Hi Alex,
thanks for the observation. I’ve fixed the bug [1]; a new snapshot
will be available tonight or tomorrow.
Best,
Christian
[1]
https://github.com/BaseXdb/basex/commit/ef2b19dab6308aeaee130d4fdc7935027dec4003
___
2013/9/18 alxarch :
> There seems to be an unexpec
Hi Anand (cc @ basex-talk),
> Yesterday, in the mailing list you have mentioned certain NEW fixes for
> 7.7.1.
> I am more concerned about
>
> CORE
> ? OutOfMemory exceptions are avoided when building large databases
>
>
> Can you explain it in details? I mean the size of "large databases"...
Joh
Hi Daniël,
the XQuery 3.1 grammar has not been finalized yet, but I agree that
our implementation is not what one would expect. I have tracked your
observation [1] and will let you know when a fix is available.
Thanks,
Christian
[1] https://github.com/BaseXdb/basex/issues/755
__
check out the latest snapshot [1]...
Best,
Christian
[1] http://files.basex.org/releases/latest/
___
2013/9/18 Daniël Knippers :
>
> I'm already glad it's been picked up this quickly.
>
> -- Daniël
>
> On Wed, Sep 18, 2013 at 9:28 PM, Christian
Good catch, has been fixed; attributes without namespace are now
ignored in the check [1]. I’ve uploaded a new snapsho.
Thanks,
Christian
[1]
https://github.com/BaseXdb/basex/commit/a587e8c9640f79fd5b5c943356164cea48a0a614
[2] http://files.basex.org/releases/latest/
___
Dear Simon,
sorry for letting you wait.
> this is rather a general question than a concrete issue or a bug report:
> Does baseX provide any snapshoting-alike functionality, i.e. the possibility
> to automatically save (potentially) affected elements
> *before* an updating transaction is performed
Hi John,
XQuery defines three set operators, namely "union", "intersect" and
"except". As those are not BaseX-specific, you’ll need to check out
other literature on XQuery
Hope this helps,
Christian
___
2013/9/24 John Best :
> Hi all,
>
> Where can I find examples using s
Hi Wendell,
RESTXQ results won’t be cached in BaseX; instead, we usually work with
proxies such as Nginx when performance is critical. Jetty may as well
be used to speed up data transfer (responses can e.g. be compressed if
the client supports it).
When it comes to performance… Do you already enc
> Any chance of getting, in addition to the per-file progress, the overall
> progress of creating the database?
...currently no, because we’re not counting all files before
retrieving them (this can take quite a while when e.g. a network
resource is addressed, or if a ZIP file from a remote URL is
Dear Yoann,
I tried to reproduce your example, using the following query:
$session = new Session("localhost", 1984, "admin", "admin");
$xml = $session->execute("XQUERY ");
print $xml;
$session->execute("XQUERY insert node $xml into ");
$session->close();
This one runs without problems on my mach
> Can these options be implemented.. ??
Yes, they could be implemented, but it may take a while to find a good
formalization of all possible choices. Your suggestions are welcome.
___
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mai
Thanks Arto for the interesting comparisons.
One more rewriting for map2 could be..
declare function local:map2($a, $b) {
let $m2 := map:new($b ! map:entry(., true()))
return $a[$m2(.)]
};
..but my assumption is that all rewritings should yield similar
performance, because the flwor
Hi France,
sorry for the inconvenience. Regarding REST(XQ) calls to the same
BaseX instance, it’s indeed sth. that should be avoided, as it can
cause all kinds of deadlocks, so it’s generally wise to address
resources outside the database when using XSLT from an updating XQuery
script. As you wrot
Hi Stefan,
we’re currently restructuring our deployments to save some more time;
the debian package for BaseX 7.7.1 or 7.7.2 will be released in near
future.
Thanks,
Christian
___
2013/9/26 Stefan Koch :
> Dear Basex Team,
>
> any plans when the debian package for version
> But one thing, I think, is missing and that is the Window/Distance Options
> for proximity search.
Feel free to add more details here:
https://github.com/BaseXdb/basex/issues/762
___
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https:
Hi George,
I’m not sure if your queries are using the full-text at all, as a
minimum of 8 seconds doesn’t sound that thrilling. Could you please
check the output in the InfoView panel in the GUI (or the command-line
output created via -V) and see what’s written there? Next, feel free
to pass us on
Timing:
> - Parsing: 0.0 ms
> - Compiling: 0.27 ms
> - Evaluating: 21324.7 ms
> - Printing: 167.93 ms
> - Total Time: 21492.91 ms
>
> Query plan:
>
>
>
>
>
>
>
>
>
>
>
> Regar
The issue has been fixed; it occurred whenever the $path string ended
with a slash. Please check out the latest snapshot [1].
I haven’t forgotten your longer mail..
Christian
[1] http://files.basex.org/releases/latest/
2013/9/30 France Baril :
> I'm currently on 7.7.
>
> The second function ret
Hi France,
you should get the desired result by adding the following line to the
beginning of your query:
declare option output:indent 'no';
Hope this helps,
Christian
PS: I’ll try my best to answer your pending mail tomorrow.
___
2013/10/5 France Baril :
> Hi,
>
> I'
Hi Alex,
thanks for your mail, and sorry for the late reply.
Currently, I can’t think of any workaround, so I’ve added your feature
request to our bug tracker [1].
All the best,
Christian
[1] https://github.com/BaseXdb/basex/issues/765
___
2013/10/1 Alexander Ryabov :
>
> I tried that, I figured it was not supported:
> [XQST0108] No output declarations allowed in library modules.
True, this is a restriction of the XQuery 3.0 specification. However,
output declarations are allowed in main modules, and since 7.7, you
can specify your RESTXQ functions both in librar
Dear all,
a new minor BaseX release is available; it provides the following new
features and fixes:
XQUERY
• a CSV Module and serialization was added
• the JSON serializer was updated (more to follow!)
• some update checks in the modify clause were fixed
• parsing of new map syntax was fixed (ign
___
2013/10/7 Christian Grün :
>> I tried that, I figured it was not supported:
>> [XQST0108] No output declarations allowed in library modules.
>
> True, this is a restriction of the XQuery 3.0 specification. However,
> output declarations are allowed in main module
> Or should I convert all modules with functions that are not using rest path
> to main modules so I can declare the output option?
Well, similar to that (I hope I got you right)... You can convert all
of your modules, which include RESTXQ annotations, to main modules. A
main module needs to end w
Hi Mike,
thanks for your mail. You are talking about an interesting issue: some
time ago, we already thought about recreating archives that had been
unpacked in the import step. This would e.g. also be helpful when
processing Office documents.
Currently, you’ll have to resort to XQuery to create
Hi Mike,
> PS: how can I post this text to your answer so that it appears in the
> posting thread?
Just reply to the mailing list.
> Thank you for answering my mail. In an other case I did in fact use the
> archive module to zip XML files into an Excel file (xlsx) and it did the job
> really goo
Hi Marco,
yes, the 7.7 behavior is correct, it’s the result from a recent W3
decision [1]. You’ll probably have to rewrite your query as follows:
Hope this helps,
Christian
[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=22032S
___
2013/10/9 Marco Lettere :
> Hell
Hi Jeremy,
there’s a good chance that regex will be supported in a future version
of RESTXQ and, thus, BaseX. You are invited to join the discussion in
the EXQuery GitHub repository [1, 2]! I guess, e.g., that some time
needs to be spent to define how conflicting paths are to be resolved
[3].
Bes
Hi Erdal,
execution times are generally highly dependent on the queries you are
working with, but in the given case, you may get better performance by
directly calling QueryProcessor.iter() instead of
QueryProcessor.execute(). Btw, I’m not sure where to find the
Result.iter() function? Do you refe
> So, calling QueryProcessor.execute() AND after that calling
> QueryProcessor.iter/value() does the work twice?
> I.e., to get the result, I do not need to execute() the query, but instead
> directly call QueryProcessor.iter() or QueryProcessor.value()?
Well, yes… Just try ;)
Hi Lars,
thanks for your observation, which sounds undesirable. Could you
please tell us which distribution (zip, debian, suse, source code, ..)
you are working with?
Best,
Christian
___
2013/10/14 Lars Johnsen :
> BaseX is installed by administrators on one of our server
Hi Jeremy,
it’s somewhat surprising, but XQuery itself has no database semantics.
This is the reason why the implementation of fn:collection is pretty
much implementation-defined [1]. In BaseX, the function checks if the
specified URI matches a database. If negative, the URI will be
resolved again
Hi Jeremy,
> Is there a method to
> open a subset of documents (not distinguishable by path) in the database
> with performance similar to calling db:open($db_name)?
Is there any criteria regarding the documents you want to open? If you
simply want to choose the first 10 documents, you could try
ncing performance problems
> since I need to iterate over the list in order to filter or choose which
> documents to open.
>
> Thanks,
>
> Jeremy
>
>
> On Thu, Oct 17, 2013 at 10:18 AM, Christian Grün
> wrote:
>>
>> Hi Jeremy,
>>
>> > Is th
Hi Florian,
> declare %restxq:path("anyPath") function {
>"Some XQuery Code",
> xmlns:restxq="http://exquery.org/ns/restxq";>/restxq/anyOtherPath
> };
please note that redirects cannot be mixed with additional output.
Instead, what you can e.g. do is to perform updates and then use a
red
> When querying a DOM Node (from DB on file system, i.e. no in memory DB)
> using QueryProcessor command: will the whole Node be fetched from the
> database or will parts of the Node's children still access the file system
> if not loaded yet?
I’m not sure what you refer to with DOM: if you use th
nces, you will get
complete copies of the original nodes in main memory, so this might be
what you need.
> 2013/10/19 Christian Grün
>>
>> > When querying a DOM Node (from DB on file system, i.e. no in memory DB)
>> > using QueryProcessor command: will the whole Node
Hi Narashimham,
If you haven’t see it yet, the Wiki page on transactions will give you
some insight how locking works in BaseX [1]. Do all of your modules
run in the same JVM, and have you ensured that all operations use the
same context? If yes, feel free to send us your sample code that
demonstr
Hi Erdal,
parsing and compilation phase is pretty fast in BaseX. Before you
think about precompiling your queries, it would be interesting to know
if parsing and compilation is a real bottleneck.. Have you already
done some profiling?
The following example of running a (very simple) query 100'000
e able to cache compiled expressions (like parsing/compiling
> regex in java).
>
> Thanks!
>
>
> 2013/10/22 Christian Grün
>>
>> Hi Erdal,
>>
>> parsing and compilation phase is pretty fast in BaseX. Before you
>> think about precompiling your quer
Hi Elangovan,
> I am using BaseX to evaluate Xpaths (Xqueries) for larger size of XML files.
> I have created BaseX database initially using CreateDB.execute(ctx) API.
What do you mean with "CreateDB.execute(ctx) API"? Could you provide
us with a minimized example?
Best,
Christian
>
> And ever
Hi Erdal,
the serialization parameter "cdata-section-elements" will help you:
http://docs.basex.org/wiki/Serialization
Best,
Christian
___
2013/10/24 Erdal Karaca :
> Hi all,
> When using parse-xml(-fragment), wrapping CDATA sections are removed and the
> text content
Hi Erdal,
similar to Wendell, I’m not quite sure what’s your actual reason for
using CDATA elements, the parse-xml() function etc. Talking about your
example..
> replace(replace('{abc}',
> '\{', '{{'),'\}', '}}')
..would you like to interpret "abc" as XQuery?
Christian
_
Hi Erol,
I can also imagine various use cases in which multithreading would be
beneficial. Have you already thought about ways how multithreaded
execution could work in XQuery?
Christian
2013/10/24 Erol Akarsu :
> I am working on crawling data. I can see it i
Hi France,
> I have a nice file with just the correct indent, that I was able to create
> by adding the xml:space="preserve" attribute to the root before making my
> inserts. [From previous thread]
good to hear.
> file:write('file.xml', $clean-file, $param), where param contains
> indent="no". I
> For example, I have big load of urls to crawl. Urls can be split to multiple
> chunks. Basex can start multiple function calls in parallel that deals one
> chunk.
> After functions finished, we can merge results. This is basic way.
Haskell provides the Strategies library for that:
http://hac
Hi Rob,
> When using a trace-instruction, like this: let $dum := trace(
> $local:programName, 'programmaNaam: '), in a Xquery program in the
> BaseX-GUI
>
> I get pre-evaluating information of some functions mixed with my trace
> output in the Query-Info-window, see below.
The Info View will alw
e instruction in 7.8 version. I sure helps my
> debugging this 200kB monster. However a good debugger would help much more
> ;-)) ( sorry, old cow but I couldn't resist )
>
> Regards,
> Rob
>
> -Oorspronkelijk bericht-
> Van: Christian Grün [mailto:christian.gr..
Hi John,
I think you’ll be glad to check out the latest extensions of the
ft:search functions [1]. Feel free to check out the 7.8 snapshot.
Christian
[1] http://docs.basex.org/wiki/Full-Text_Module#ft:search
___
2013/9/26 John Best :
> Dear Christian,
>
> The syntax of t
Hi Zach,
thanks for your long e-mail, and your offer to add WKB support to the
Geo Module. I absolutely agree that it would be nice to have support
for other Geo format. The main reason for the GML support is that we
didn’t have time yet to adopt other standards.
We are looking forward to your im
> - Read external file which contains user provided contents (maybe, with
> curly braces in some text contents or embedded in CDATA sections)
> - Replace an existing node in DB with the read xml fragment using
> parse-xml-fragment()
Why don’t you do something like..
let $xml := doc("external-fi
> Problem 1:
> [...]
> If I open two ( small) packages of which one has no errors and one has
> errors then the errorstatus-message at the bottom of the editor doesn’t
> synchronize correctly when switching files.
Just to be sure: what do you mean with packages? do you refer to
XQuery library modu
> Improper use? Potential bug? Your feedback is welcome:
> [...]
> Contact: basex-talk@mailman.uni-konstanz.de
Can you also provide an example query that triggered this exception?
___
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mai
Hi Zachary,
a short one: I wouldn’t recommend to break the existing API, as
implementation independence is something EXPath is all about. Instead,
I would vote for a unified XML representation of the geometry objects,
which can then be interpreted by the Geo functions. Converting XML to
objects an
Hi Werner,
thanks for writing to the list.
I currently have no idea what changes may have led to the
incompatibility you’re describing in your mail. Could you provide us
with a little example script that allows us to reproduce the behavior?
Thanks in advance,
Christian
__
501 - 600 of 5088 matches
Mail list logo
