This release further improves support for the just released beta of Sphinx 2.1 by allowing users to save JSON attributes to real-time indexes with the fluent API. The fluent API now also supports new query options and the creation of snippets within a query via the GetSnippets() extension method.

The native API has gotten support for new query flags and sub-selects introduced with Sphinx 2.1. A list of all changes is available in the version history.

We're pleased to announce the immediate availability of a new release of SphinxConnector.NET! Among other things, we've been busy to add support for Sphinx 2.1 in the course of which we've made several optimizations that should improve performance and reduce memory usage with SphinxQL and the fluent API.

The latter now properly supports enums and has gotten support for JSON attributes that are going to be introduced with Sphinx 2.1. The methods First() and FirstOrDefault() can now also be executed as futures, and we've added the possibility to perform operations like attaching and flushing indexes to the fluent API.

There are several other additions, improvements, and bugfixes which are listed in the version history.

SphinxConnector.NET 3.1.3 has just been made available for download and via NuGet. A list of resolved issues is available in the version history.

We're pleased to announce the immediate availability of SphinxConnector.NET 3.1!

This version introduces support for future queries with the fluent query API. This feature allows to defer the execution of queries until their results are needed, enabling SphinxConnector.NET to send them in batches. This functionality is available with .NET 4.0 or higher and Mono.

Additional improvements to the fluent query API:

• IFulltextQuery.Where can now be called multiple times for a query.
• The generic type of collections for multi-value attributes e.g. IList<T> etc. can now be of any type that is large enough to hold the result values. Previously only 'long' was supported.
• A workaround to the query generator has been added, to account for the fact that Sphinx currently doesn't support using 'weight()' in an expression, e.g. 'SELECT weight()*2 AS c1 FROM example'. The query generator will now emit a separate, aliased weight() column and use the alias in the expression, e.g. 'SELECT weight() AS c2, c2*2 AS c1 FROM example'.

Last but not least, a bug that caused the RecordsAffected property of the SphinxQLDataReader class not being set correctly when the reader was used to read results from multiple SELECT or SHOW statements, has been fixed.

A new version of SphinxConnector.NET 3.0 has been released. This version fixes a race condition that could occur when closing a pooled connection. Additionally a new version of the 2.x branch is available. This is a bugfix release that contains fixes that were backported from the 3.x branch.