0.5.0

This is the first release in the series LDP 0.5.

Please note that all releases earlier than LDP 1.0 are for testing purposes and are not intended for production use. Releases earlier than LDP 1.0 also do not support database migration, so that it may be necessary to create a new database when upgrading to a new release.

Release notes (since 0.4.0):

• Tables have been renamed to include a domain prefix, following the pattern <domain>_<table>. This is a breaking change that has been introduced to improve schema organization and reduce namespace collisions.

0.4.1

This is an update to the LDP 0.4 release. Please note that all releases earlier than LDP 1.0 are for testing purposes and are not intended for production use. Releases earlier than LDP 1.0 also do not support database migration, so that it may be necessary to create a new database when upgrading to a new release.

Release notes:

• This release contains updates to documentation.

0.4.0

This is the first release in the series LDP 0.4.

Please note that all releases earlier than LDP 1.0 are for testing purposes and are not intended for production use. Releases earlier than LDP 1.0 also do not support database migration, so that it may be necessary to create a new database when upgrading to a new release.

Release notes (since 0.3.0):

• Support for historical data has been added.
• New tables, addresstypes and proxiesfor, have been added.
• Experimental support for large-data extraction, to work around current limitations of module interfaces.
• Improved handling of cases where data record sizes exceed Redshift data type limits.
• A new attribute, tenant_id, has been added for future use in consortial reporting.
• A bug has been fixed that caused tables not to be updated when an extraction succeeded with zero records.
• The databaseUser configuration parameter has been renamed to ldpAdmin, and databasePassword has been renamed to ldpAdminPassword.
• Changes to the command line interface for loading data and the configuration file format.

0.3.15

This is an update to the LDP 0.3 release. Please note that all releases earlier than LDP 1.0 are for testing purposes and are not intended for production use. Releases earlier than LDP 1.0 also do not support database migration, so that it may be necessary to create a new database when upgrading to a new release.

Release notes:

• A compilation error under GCC has been fixed.

0.3.14

This is an update to the LDP 0.3 release. Please note that all releases earlier than LDP 1.0 are for testing purposes and are not intended for production use. Releases earlier than LDP 1.0 also do not support database migration, so that it may be necessary to create a new database when upgrading to a new release.

Release notes:

• New tables, addresstypes and proxiesfor, have been added.

0.3.13

This is an update to the LDP 0.3 release. Please note that all releases earlier than LDP 1.0 are for testing purposes and are not intended for production use. Releases earlier than LDP 1.0 also do not support database migration, so that it may be necessary to create a new database when upgrading to a new release.

Release notes:

• The ldp schema has been renamed to ldp_catalog.
• Various minor schema changes and documentation updates.

0.3.12

This is an update to the LDP 0.3 release. Please note that all releases earlier than LDP 1.0 are for testing purposes and are not intended for production use. Releases earlier than LDP 1.0 also do not support database migration, so that it may be necessary to create a new database when upgrading to a new release.

Release notes:

• A new attribute, tenant_id, has been added for future use in consortial reporting.
• The sys.loading table has been renamed to ldp.table_updates.
• A few minor adjustments have been made to history table constraints.
• Query examples on historical data have been added to the LDP User Guide.

0.3.11

This is an update to the LDP 0.3 release. Please note that all releases earlier than LDP 1.0 are for testing purposes and are not intended for production use. Releases earlier than LDP 1.0 also do not support database migration, so that it may be necessary to create a new database when upgrading to a new release.

Release notes:

• A bug has been fixed that caused tables not to be updated when an extraction succeeded with zero records.
• Status updates in sys.status have been disabled due to a locking issue in Redshift. The table, sys.loading, can be used instead.
• A few preliminary notes on Redshift database configuration have been added to the LDP Admin Guide.

0.3.10

This is an update to the LDP 0.3 release. Please note that all releases earlier than LDP 1.0 are for testing purposes and are not intended for production use. Releases earlier than LDP 1.0 also do not support database migration, so that it may be necessary to create a new database when upgrading to a new release.

Release notes:

• The target configuration parameter, ldpUser, is no longer required, and its value defaults to ldp.

0.3.9

This is an update to the LDP 0.3 release. Please note that all releases earlier than LDP 1.0 are for testing purposes and are not intended for production use. Releases earlier than LDP 1.0 also do not support database migration, so that it may be necessary to create a new database when upgrading to a new release.

Release notes:

• The data loading status for each table can now be viewed with: SELECT * FROM sys.status;. Tables that have been updated in the past 24 hours are labeled as "OK". This replaces the table, sys.zz_loading.
• The LDP database user is now specified via a configuration parameter, ldpUser.
• The databaseUser configuration parameter has been renamed to ldpAdmin, and databasePassword has been renamed to ldpAdminPassword.