Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop record states #27

Merged
merged 3 commits into from
Jan 16, 2018
Merged

Drop record states #27

merged 3 commits into from
Jan 16, 2018

Conversation

danpalmer
Copy link
Contributor

This is temporary. There is an ongoing discussion about the best data export format.

  • 2e91adc brings the data model up to date to what we currently think it should be.
  • d8a33d8 removes the models and all related functionality in one go.

When work starts to re-introduce this, reverting d8a33d8 should provide a good starting point with failing tests.

Column('name', String, primary_key=True),
Column('updated', DateTime),
Column('id', Integer, primary_key=True, autoincrement=True),
Column('name', String),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While I'm not sure what model we're after, I wonder whether this column should be unique?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not for what James and I were trying to get to when we came up with this iteration. Old state machines would not be resurrected, a new one would be created.

@danpalmer danpalmer merged commit 366b127 into master Jan 16, 2018
@danpalmer danpalmer deleted the drop-record-states branch January 16, 2018 17:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants