3.11.0 (2022-05-05)

This release adds support for some of the most oft-requested Leaf features! Specifically:

1. Support for database vendors besides SQL Server
2. Support for App and Clinical databases on separate servers

New Features

• #300 - The specific database vendors supported are:
  

  • MySQL
  • MariaDB
  • PostgreSQL
  • Oracle
  • Google BigQuery
  • SQL Server

  To specify your database vendor, set the new Db.Clin.RDBMS property in the appsettings.json file:
  

  If using Google BigQuery for RDBMS, your LEAF_CLIN_DB environment variable should be your BigQuery ProjectId, rather than a connection string. Leaf further assumes that you also have a GOOGLE_APPLICATION_CREDENTIALS environment variable and associated key.json file. See https://cloud.google.com/docs/authentication#getting_credentials_for_server-centric_flow for more information.

  Note that Db.Clin.RDBMS is required, even if you are planning to (continue) using SQL Server.

• #514 - Related to support for new database flavors, this also enables the App and Clinical databases to be deployed to separate databases servers (which is required if not using SQL Server, else optional).

• #513 - The Visualize and Patient List screens can now be enabled, even when LowCellMasking is on. Special thanks to @artgoldberg and @glabrie10 for invaluable implementation suggestions and ideas.

Minor changes

• #489 - The Patient List "+ Add More Data" modal now defaults to "Anytime" (previously was "Past 6 Months").

Upgrading to 3.11.0

1. Client app and server API - Download and deploy the latest client and server compiled files under Assets, included in this release (or compile on your own as described in the Leaf installation instructions), making sure to first remove any previously deployed instances.
2. Database - execute the 3.10.1__3.11.0 database update script on your Leaf application database.
3. appsettings.json - Update the appsettings file as specified above.