Hi Steve,
A rather late reply to [1] (but maybe better than fully ignore it): We
have fully revised our quality factor handling. The best RESTXQ
function candidates will now be chosen in multiple steps, and your old
use case (with wildcard content types) should now work as expected. If
you still
;
Cc: BaseX <basex-talk@mailman.uni-konstanz.de>
Sent: Tuesday, November 22, 2016 1:19 PM
Subject: Re: [basex-talk] Preparing BaseX 8.5.4 (please don't forget Issue
#1341)
I'm also wondering about the issuehttps://github.com/BaseXdb/basex/issues/1220
which prevents usingBaseXHttp for c
Yes, we definitely need to find more time for open source development
again. Talking about 1220, I can’t promise anything for now.
Unfortunately, the open source part is exactly that part of our work
which isn’t financed by anybody, but which everybody asks for (unless
we are talking about
I'm also wondering about the issue
https://github.com/BaseXdb/basex/issues/1220 which prevents using
BaseXHttp for content negotiation. I realize that you have to
prioritize what gets fixed in the releases. However, I probably should
make a decision about whether to plan on using BaseXHttp
Hi Jan,
> Please don't forget to fix issue: SQL with BaseX 8.5.3 #1341
I can’t promise anything for now reg. this patch release, but we’ll do
our best to release BaseX 8.6 pretty soon.
Cheers
Christian
Hi,
we noticed you prepare release 8.5.4.
Please don't forget to fix issue: SQL with BaseX 8.5.3 #1341
Thx
Jan
--
Jan Dölle
E-Mail: basex-l...@id1.de Telefon +49-69-244502-0 Home: www.id1.de
Information Design One AG, Baseler Straße 10, 60329 Frankfurt am Main
Registereintrag: Amtsgericht
6 matches
Mail list logo
