| 739212) |
|
| Georgianna |
| georgiannacline769(at)charter.net |
Ort: Koallah |
|
Its fluent interface has been designed for great usability and ease of use.
Even probably the most complex queries might be created simply without writing a single line of SphinxQL with the LINQ-like question API. It makes you more productive, your code becomes easier to maintain and is less complicated to refactor. You can save and delete paperwork in actual-time indexes with simply a technique name.
By utilizing a convention primarily based approach, the time you spend on configuration is lowered to a minimum. It keeps your code freed from custom attributes, requires no manual object mappings and things generally work out of the box. It would not drive you to create handbook mappings to your objects, you do not have to use some clunky designer, setup is minimal: It just will get out of your way.
The fluent query API permits each newbies and advanced users to easily design their full-textual content queries. Support for options introduced in 0.9.9 like: - Persistent connections: open one connection for several operations to reduce network overhead. Override attributes: briefly change the value of an attribute without modifying the precise value for superior search situations.
Please observe that the native API is only meant to support legacy projects and was eliminated in SphinxConnector .Net 6.0. New projects should use the fluent API or SphinxQL. Thanks a lot! The support was actually helpful and answered our questions actually quick.
|