This minor release of ODM2.0 fixes a number of spelling errors to field and table names and supports the use of the PostgreSQL UUID datatype, rather than the deprecated UniqueID/OID datatype.
This release will support work on a simplified and modernized version of the ODM2PythonAPI, that is designed for Python 3.7 takes advantage of the full power of the latest version of SQLAlchemy). We're doing this ODM2PythonAPI development in a forked branch at https://github.com/LimnoTech/ODM2PythonAPI/tree/python37update.
Warning:
This minor release will break compatibility with most components of the existing ODM2 software stack, including some components of this repository.
Specifically, ODM201_for_PostgreSQL_manySchemas.sql is the only one of the blank_schema_scripts to be updated to reflect the v2.0.1 changes. Furthermore, this script was directly generated from DBWrench (v4.25), preserving the CamelCase naming conventions and the many database schemas of the ODM2 design. This diverges from the previous approach of stripping these features to enable broad compatibility with other RDBMS software (i.e. MySQL). We are thus moving toward dropping support for MySQL and MS SQLServer in order to develop better support for modern versions of PostgreSQL and eventually also SQLite.
If you need full ODM2 software system compatibility, please stick with our ODM2 v2.0.0 release
Improvements:
- Switched
UniqueID(OID) datatypes, which have been deprecated in PostgreSQL, to theUUIDdatatype, as described in #157.
Bug Fixes:
- Fixed a number of spelling errors, to
IdentifierandPositionfields & table names.
For details of all these changes, see the code "diff" views for each of the commits listed in PR #154 .