SphinxQL: New connection string option Encoding. This option sets the encoding that is used for both queries and result sets. The option Result Encoding is now obsolete.

The default encoding is now utf-8. In previous version it defaulted to latin1, which could cause problems, because most indexes are configured to use utf-8 as charset type. The reason the encoding has to be configured in the first place, is because Sphinx currently uses a hardcoded value of latin1 for the charset type of SphinxQL result packets.

The behavior of SphinxQLParameterCollection.Add(object value) and Contains(object value) did not match other data providers: The given parameter was interpreted as the value, that the Value property of a SphinxQLParameter instance should be set to, i.e. Add() would a create new parameter object with the specified value, and Contains() would check the collection for a parameter with the specified value.

This is the correct behavior according to the documentation of the base class, DbParameterCollection, but other data providers expect value to be an instance of the respective parameter class. Passing a value that is not a SphinxQLParameter, will not throw an exception, but trigger the old behavior and log a warning. This will be removed in a future release.