Release Notes: This release adds a new select function to get the year of a date. It changes the data upgrade process and adds a new method to WikittyClient and BusinessHelper to remove an extension easily. Wikitty now uses SolR 4.1, and solrconfig.xml has been cleaned up. The select implementation have been changed to do only one solr request. New methods are supported in the query language. WikittyQueryResult has been improved. Wikitty now supports relative dates for String date representation. This version also fixes a bug corrupting the solr index when using multiple instances on the same data file.
Release Notes: This release allows you to remove an extension on a wikitty object. You can add a default value tag for wikitty field definition. The parser has been enhanced to support an empty query as True and #depth as WikittyFieldSearchDepth. A DISTINCT clause has been added for SELECT queries. The select clause has been enhanced to allow multiple select and user functions. A format translator has been added in the query parser when the field to compare is a date. Some bugs have been fixed.
Release Notes: This release fixes bugs in search results and field order, and adds the preload option for Wikitty fields and unify methods names on BusinessEntity and Wikitty.
Release Notes: This release adds a parse and a extContainsOne method to WikittyQueryMaker. It also adds a new query property wikittyFieldSearchDepth which allows following links between wikitty for searches. You can now set a File on a binary field. A bug causing an error in the findTreeNode client method when Node depth + depth asked > Integer.MAX_VALUE has been fixed.
Release Notes: This version introduces many changes such as sort order, constraints, toString, wikitty-extension, pattern, indexed, and crypt tag-values. (Not)Equals can now ignore case and accents if needed. In QueryResult, you can get elapsed time. Parser now supports limit and offset and ' as a string delimiter. In-memory implementations have been improved. Bugs have also been fixed, including JdbcSQLException during sync engine, and all not* conditions have different behaviour with in-memory service.