steve-2.0.1

fix: HikariCP configuration

when both jdbcUrl and dataSourceClassName are set, dataSourceClassName has the higher priority during setup and
it requires setting all the necessary related properties. HikariCP will not validate config (newly fixed, see [1])
and silently initialize an 'empty' data source which fails during runtime. this fix drops the usage of jdbcUrl,
and properly and fully sets the data source properties.

[1] https://github.com/brettwooldridge/HikariCP/issues/401

steve-2.0.0

What's new?

• Download transactions as CSV in streaming mode
• Can add an additional "note" to users and charge points
• Break away from the hardcoded "stevedb" schema/db name (Configure in main.properties file)
• Break away from the requirement that the MySQL user should be "root"

To upgrade existing deployments, please see the FAQ

steve-1.3.0

switched to java 8

steve-1.2.0

filtering criteria for users table and other fixes

steve-1.1.1

add various filtering criteria for transactions and reservations tables

steve-1.0.11

always accept a start transaction regardless of idTag status

steve-1.0.10

dependency version updates and small fixes

steve-1.0.7

Fixes #5

steve-1.0.6

version bump to prepare for release

steve-1.0.5

Bug fixes related to WebSocket/JSON implementation and support for multiple strategies to choose a WebSocket session