GitLab

- Fuzzy queries now work properly even when using relative timestamps
such as "now-5m"

- Operations based on sensors with custom scaling factors would output
wrong results

- If users specify a single timestamp (startTs==endTs) when performing
a sensor query through dcdbquery or libdcdb, a fuzzy sensor query is
performed, and the closest sensor reading to the target timestamp is
returned

- Fixed a bug associated to virtual sensor queries under the new schema
- Symbol for scaling in dcdbquery is now '@'

- Now it is possible to perform queries on raw topics without doing
a lookup on the publishedsensors table, by using the -d option

Move CXXFLAGS definitions to config.mk and thus streamline compiler flags for all Makefiles in subdirectories

- String topics are now used across all of DCDB, up to Cassandra
- As of now, sensor names ALWAYS match MQTT topics
- Users can still define sensor "aliases" via dcdbconfig that point
to the same topics

- Added some more indentation to make the configurations more readable
- Fixed one more warning in dcdbquery

- Fixing a few warnings here and there in the tools subdirectory

- Added a 'common' directory where all shared code has been placed
- Analytics package has been moved out of dcdbpusher, now has its own makefile
- Some renaming here and there for uniformity

Explicitly cast arguments to DCDB:Timestamp constructor to uint64_t to avoid ambiguities with different compilers

Rework DCDBQuery::doQuery() and DCDBQuery::genOutput() to leverage proper regular expressions for function-, sensor-, and modifier-parsing.

Bugfix: Parse for functions and modifiers in a sensorname string first, then lookup the actual sensor name in the DB