[ckan-changes] [ckan/ckan] 918eeb: Adds metadata_created as a proper DB field.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/ckan/ckan
  Commit: 918eebee07c277d7a2315185adfb9f3f21a480e7
      https://github.com/ckan/ckan/commit/918eebee07c277d7a2315185adfb9f3f21a480e7
  Author: Ross Jones <ross at servercode.co.uk>
  Date:   2015-11-17 (Tue, 17 Nov 2015)

  Changed paths:
    A ckan/migration/versions/082_add_metadata_created.py
    M ckan/model/package.py

  Log Message:
  -----------
  Adds metadata_created as a proper DB field.

Currently the metadata_created is calculated on each access by querying
the package_revision table and finding the oldest revision.  There's
little advantage to this over setting the field to be a column on the
package table and defaulting to now().  This means it can be overwritten
by those components, like harvesting, that require the ability to do so
- without meddling with revisions.

This should fix #2735


  Commit: 5f18d81e0519abafddc5dd447676d484493b7794
      https://github.com/ckan/ckan/commit/5f18d81e0519abafddc5dd447676d484493b7794
  Author: Ross Jones <ross at mailbolt.com>
  Date:   2015-11-19 (Thu, 19 Nov 2015)

  Changed paths:
    M ckan/migration/versions/082_add_metadata_created.py

  Log Message:
  -----------
  Allow new metadata_created field be null

This is so that we don't set the value just to overwrite it with the UPDATE


  Commit: bd95b15f130f5312c932f1157a00ae16de4b0964
      https://github.com/ckan/ckan/commit/bd95b15f130f5312c932f1157a00ae16de4b0964
  Author: Ian Ward <ian at excess.org>
  Date:   2016-01-25 (Mon, 25 Jan 2016)

  Changed paths:
    A ckan/migration/versions/082_add_metadata_created.py
    M ckan/model/package.py

  Log Message:
  -----------
  Merge pull request #2739 from ckan/2735-metadata-created-as-field

Adds metadata_created as a proper DB field.


Compare: https://github.com/ckan/ckan/compare/f5875be08733...bd95b15f130f