Version 3.1 (Feb 1, 2010)

Enhancements

• See version 3.1beta for main changes.
• Upgraded to latest XQuery Update Candidate Recommendation (09 June 2009). Qizx 3.1 passes 100 % of tests of XQUpdate Test Suite 1.0.0.
• Automatic DOCTYPE generation when serializing a document. Can be disabled by new option auto-dtd=false.

Bug fixes

• Serialization: improper generation of default namespace from attributes.
• Query compilation issue on: $node/*[. ftcontains "..."]

Version 3.1 beta (Nov 9, 2009)

Enhancements

• Added simple full-text query syntax and several full-text convenience functions for scoring, highlighting, extracting document snippets, looking up indexes: see chapter full-text extension functions in documentation for more details.
• Improved full-text scoring speed. Document ranking (or weighting) through a meta-property ft-weight is now deprecated because too slow (this will be replaced by a more efficient mechanism in a later version).
• Added a chapter in the manual introducing the main utility classes offered by the Java API.

Bug fixes

• Miscellaneous full-text bugs detected by passing the XQFT Test Suite (results to be published by W3C).
• Opening an XML Library Group twice was throwing an unclear exception on Windows. This exception now explicitly tells that only one instance of LibraryManager can exist for a Library Group at a time.
• XQuery Update: updates performed within an (updating) function were often lost.
• Calling Library.createCollection(path), where path has no leading slash, provoked an infinite loop.
• Several inefficiencies and memory leaks (yet unreported).

Version 3.0 (May 20, 2009)

Bug fixes

• A noxious bug that appeared under very heavy load, with many threads performing transactions concurrently, and that could corrupt an XML Library (reported by Lóránt Pintér).

  This new version has been tested with over 200 threads.

• Introduced a limit to the number of index segments created when a large number of threads perform transactions simultaneously. The multiplication of index segments increases memory consumption and could provoke OutOfMemoryException's.

  Also fixed 2 memory leaks contributing to these OOME.

Enhancements

• Improved crash recovery and database sanity checks.

Version 3.0 beta (March 9, 2009)

Enhancements

• Support of the standard XQuery Full-Text functionalities. This new W3C Recommendation provides a comprehensive specification for full-text search, well integrated with the XQuery language.

  The new full-text functionalities in Qizx are a nearly complete implementation of the standard, with an execution speed slightly improved with respect to the former implementation. Documentation can be found in the User's Manual section of the documentation. A new tutorial is available here if you wish to get acquainted with this language extension.

  Attention: the former support of full-text in Qizx 2.x, based on extension functions, has been completely withdrawn. To help migrating your applications, we have written a dedicated chapter in the documentation: "Migration Guide from former Full-Text implementation". Version 3.1 might restore the former full-text functions as a layer on top of new full-text, but only if we feel a demand from our users.

• Due to the new full-text, Indexing Specifications have slightly changed: "word sieves" are deprecated. The Java API contains a new package com.qizx.api.fulltext that provides means of customizing full-text features (tokenization, stemming, thesaurus, scoring).
• Miscellaneous optimizations. As a result, Qizx 3.0 is about 40% faster on the XMark benchmark. More details can be found in the chapter "Writing efficient queries" of the Developer's Manual.

Bug fixes

• A speed regression was introduced in 2.2 in function count() when access-control is not used.

• Data conversions in Indexing Specifications were not used when the query is not indexable, leading to inconsistent execution errors.

  Note: this data conversion mechanism is actually an extension of XQuery and goes beyond XML Schema. It is not yet available in Qizx/open.

  For example assuming that Indexing Specifications are able to recognize and convert dates written like "12/31/99" in element and attributes values, a non-indexable query like //*[date = xs:date("1999-12-31")] did generate an error, whereas the indexable query //event[date = xs:date("1999-12-31")] was working as expected.

• Issue when loading a module in the current directory when no location is provided.

Version 2.2 (November 24, 2008)

New Licenses and new pricing

Qizx 2.2 has a new licensing scheme and a new price list.

Enhancements

• Support of XQuery 1.1 features: the very useful and long awaited group by in FLWOR, and the for window clause which allows "chunking" a sequence based on conditions.
• The documentation "Getting Started" now includes a section about XQuery Update.

Bug fixes

• XQuery join optimization: a join using the operator "<" could miss a result item due to improper bound test.
• XQuery: built-in functions handling the type xs:anyUri (for example fn:resolve-uri) had type inconsistencies that could create surprising run-time type errors.

• XQuery Update: Updating Expressions within most operators (except FLOWR, if, typeswitch, comma) are illegal but errors were not raised. As a consequence, some (invalid) expressions silently failed to execute. For example an Updating Expression within a node constructor, which is not allowed by the language, could not be executed.

• Java API: inconsistencies in ItemSequence counts and positions when Access Control is used.

  countItems() was counting nodes barred by Access Control, skip() was not consistent with moveToNextItem(). Now all methods take AccessControl into account, possibly with some speed penalty.

• Java API: using a dangling Node of an actually deleted document was generating obscure exceptions. A DataModelException with message "deleted document" should now be raised. Notice it might happen that in-cache Nodes still be accessible even though their document is deleted.
• XML Library engine: an error "bad block mark" was sometimes appearing when performing commit operations at high speed (for example: doing a massive number of document imports each followed immediately by a commit, which is definitely not a recommended practice).
• XML Library engine: Library.deleteMember had caching issues before a commit was done.

  for example deleteMember("/a") followed by renameMember("/b", "/a") generated an error claiming that "/a" was still existing.

• XML Library engine: Library.renameMember had caching issues before a commit was done. If a document was first accessed, then renamed (or if an enclosing collection was renamed), then the getMember or getDocument methods could return stale handles still having the old path. Similar issue for collections.
• Serialization bug in Indexing specifications, built programmatically and using names with namespaces: could prevent re-opening an XML Library.

Version 2.1 (May 21, 2008)

1. XQuery Update: Qizx 2.1 fully supports the XQuery Update Facility draft specifications.

   This implementation passes 100% of the current XQUF Test Suite.

2. Qizx Studio improvements:
   • New editing dialog allows easier definition of most frequent customizations of Indexing Specifications.
   • Progress bars for database operations like re-indexing and index compaction. These operations are now synchronous (see below).
   • Miscellaneous: more graceful namespace display in XML views, new icons, directories and paths remembered, double-click in tree views performs a full expand/collapse.
3. API extensions:
   • Methods optimize and reIndex of Library become synchronous (or blocking). The LibraryProgressObserver interface is extended to include these operations (slight incompatibility).
   • New utility class PushNodeBuilder to build native in-memory Nodes, as an alternative to using DOM or XML parsing for binding Node values to XQuery global variables.
   • DOM types are now recognized in Java Binding (arguments and return value of methods) and converted (by copy) to internal Qizx representation.
   • The XQuerySession interface has a new method enableJavaBinding for making Java classes eligible for use with the Java Binding mechanism. Attention: Java Binding is no more enabled by default when using the API. It is possible, though not recommended, to allow all Java classes at once.
4. Miscellaneous:
   • Some names of built-in properties of Documents have been changed. All default built-in properties are now documented.

Version 2.0 (January 14, 2008)

First release.