Big changes in the QueryInterface

[Felix Mayerhuber]

Hi @all,

hereby I announce some big changes in the QueryInterface which have been
made. Until now the querying has been done in background based on Maps,
where the key is a property name and the value is the searched value for
this property. However, this approach was not sufficient, since a map
can not handle all features we want to provide through the
QueryInterface. So the new object QueryRequest was introduced.

This object encapsulates all necessary information for a query (if you
perform a query based on text, the text will be parsed into such an
object). Additionally to the key/value comparison parameters, the new
object allows to activate/deactivate for a query the support of
wildcards and defines if the values are case sensitive or not in the query.

This new object also revolutionize the EngineeringDatabaseService and
the QueryInterface. The interface changes are listed here:

EngineeringDatabaseService:
*) removed queryByMap method
*) changed parameters of query method from (Map, Long) to (QueryRequest)

QueryInterface:
*) removed queryForModelsAtTimestamp method
*) removed queryForModels method
*) removed queryForModelsByQueryMapAtTimestamp method
*) removed queryForModelsByQueryMap method
*) removed queryForActiveModelsByQueryMap method
*) added method with the signature (<T> List<T> query(Class<T> model,
QueryRequest request); )
*) added method with the signature (<T> List<T> queryByString(Class<T>
model, String query); )
*) added method with the signature (<T> List<T>
queryByStringAndTimestamp(Class<T> model, String query, String timestamp);)
*) added method with the signature (QueryRequest parseQueryString(String
query) throws EKBException;)

I hope you enjoy the changes and there will be more extensions with this
object in the near future : )

Kind regards
Felix