The compliment is well-deserved ;-)
Yes, after my mind settled down on what I wrote, I realized this too.
The annotation nor the anonymous function itself (a partial could have
served the same function) wasn't necessary. So it's just plain cool
instead of very cool.
It was mostly my sudden
+1 on both topics: product/team and the unit-module.
I, too, discovered the power of unit-testing and the unit-module lately. Using
the unit-module I build unit-tests to test the basic rules, the axioms, of my
modules and it works great.
It is a big help in keeping the whole thing stable.
One
Urgh, and to the list of course.
-Oorspronkelijk bericht-
Van: Rob Stapper [mailto:r.stap...@lijbrandt.nl]
Verzonden: woensdag 13 januari 2016 9:02
Aan: 'Christian Grün'
Onderwerp: RE: [basex-talk] FW: minor issue in the project-view of BaseX-GUI
with error marking
Hi Christian,
Got
Sorry, I was a little bit irritated by the given example ...
Now, with ft:tokens('db') I'll get mostly what I want, if I'm NOT using
stemming when creating the fulltext-index.
But its sorted by length of the tokens, inside length it's alphanumeric:
A
B
C
zusammenknäuelte
zusammenschütten
Yes, true. My experience is, if you want to include wildcard-searching based on
thesaurus, you have to define the entries something like this:
Brief
Brief.*
RT
Nachricht
RT
Hello,
I’m getting an unexpected behaviour with the serialization option
include-content-type and file:write with HTML.
If I write a document without a element then one doesn’t get added and
nothing happens.
file:write("test.htm",,map {"method":"html",
Hi James,
> Is this correct?
It should be, at least according to the current specification (“If
there is a head element [...]”, see [1]).
Hope this helps,
Christian
[1]
https://www.w3.org/TR/2015/CR-xslt-xquery-serialization-31-20151217/#HTML_INCLUDE-CONTENT-TYPE
On Wed, Jan 13, 2016 at
That works perfect. Thanks a lot.
> Am 13.01.2016 um 15:27 schrieb Christian Grün :
>
>> So far, I can't figure out a way to do a alphanumeric sorting of the
>> complete list by content of the entry, the token itself.
>
> Try this [1]:
>
> for $token in
Hi Christian,
Thank you for that, so the first case is correct. And the second case, where
existing elements are removed? I’ve just read the spec and it looks like
only elements that have http-equiv should be discarded.
Regards, James
> On 13 Jan 2016, at 18:31, Christian Grün
Looks suspicious indeed. Thanks for the hint, I’ll track this down
this soon [1].
Christian
[1] https://github.com/BaseXdb/basex/issues/1240
On Wed, Jan 13, 2016 at 7:37 PM, James Ball wrote:
> Hi Christian,
>
> Thank you for that, so the first case is correct. And
Christian,
Thank you.
I’ve just spotted that I was unclear in my description in the last email.
According to the specification only elements that have @http-equiv with
a value of Content-Type should be discarded. Not any with http-equiv. Apologies
for any confusion.
Regards, James
> On 13
Hello,
I need help with hopefully a simple XQUERY.
I want to extend below XQUERY to run not on all documents in all databases,
but only on those documents which contains "input string X" in its db:path
(i.e. its original file name).
Any help appreciated.
declare variable $n as xs:string
> I want to extend below XQUERY to run not on all documents in all databases,
> but only on those documents which contains "input string X" in its db:path
> (i.e. its original file name).
This should do it:
db:open('db')[contains(db:path(.), 'input string X')]
If a database has a big number
> I’ve just spotted that I was unclear in my description in the last email.
> According to the specification only elements that have @http-equiv
> with a value of Content-Type should be discarded. Not any with http-equiv.
> Apologies for any confusion.
No reason to be sorry; I should simply
** thanks ** fixed ** in ** the ** latest ** snapshot **
On Wed, Jan 13, 2016 at 3:26 PM, Andy Bunce wrote:
> Hi,
>
> Query:
> contains("aaa","ab",
> 'http://www.w3.org/2005/xpath-functions/collation/html-ascii-case-insensitive')
>
> Improper use? Potential bug? Your
Hi,
Query:
contains("aaa","ab", '
http://www.w3.org/2005/xpath-functions/collation/html-ascii-case-insensitive
')
Improper use? Potential bug? Your feedback is welcome:
Contact: basex-talk@mailman.uni-konstanz.de
Version: BaseX 8.4 beta 1814d39
Java: Oracle Corporation, 1.8.0_45
OS: Windows 8.1,
> So far, I can't figure out a way to do a alphanumeric sorting of the complete
> list by content of the entry, the token itself.
Try this [1]:
for $token in ft:tokens('factbook')
order by $token collation '?lang=de'
return $token
[1] http://docs.basex.org/wiki/Full-Text#Collations
17 matches
Mail list logo