Skip to content

Add support for version comparisons with database format #22

Open

Description

@kyleniemeyer
No description provided.

Activity

  1. added this to the v0.1 milestone on Sep 17, 2016
  2. self-assigned this
    on Sep 18, 2016
  3. bryanwweber commented on Nov 25, 2016

    @bryanwweber
    Member

    I'm not sure what this actually entails. Should features be disabled if an "old" version of the database is specified? That seems pretty complicated, let alone trying to have totally different behavior of the same feature if a specific database schema version is specified. I vote to push this to at least 1.0, and generally, to try our best to avoid backwards-incompatible changes to the database schema.

  4. kyleniemeyer commented on Nov 26, 2016

    @kyleniemeyer
    MemberAuthor

    I'm not quite sure either. I believe we were thinking more along the lines of specifying the ChemKED (CK? CKED?) format used when creating the file, so that the PyKED could check it and gracefully handle any breaking changes. That does seem like it would be complicated, though.

    I agree that this can be pushed off to 1.0. Ideally, we should be able to only add new features, rather than change or delete things, starting at that point.

  5. modified the milestones: v1.0, v0.1 on Nov 26, 2016
  6. removed their assignment
    on Jan 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions