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.

Sign up for GitHub

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

Jump to bottom

Paper Trail or Custom Versioning? #188

Closed
edpaget opened this issue Oct 7, 2014 · 2 comments
Closed

Paper Trail or Custom Versioning? #188

edpaget opened this issue Oct 7, 2014 · 2 comments
Labels
question

Comments

@edpaget
Copy link
Contributor

edpaget commented Oct 7, 2014

We have a few fields in models that need versioning:

  • ProjectContent
    • description
    • pages
    • example_strings
  • WorkflowContent
    • strings
  • Subject
    • metadata
    • locations(?)

Almost all of these are just going to be blobs of JSON.
@edpaget edpaget mentioned this issue Oct 7, 2014
Closed
@camallen
Copy link
Contributor

camallen commented Oct 7, 2014

If we need the bells and whistles then paper trail is a pretty solid solution. That said if we're just storing and reporting old versions then our own would probably suffice.

Seems paper trail supports JSON postgres data types:
paper-trail-gem/paper_trail#287
paper-trail-gem/paper_trail@9500429

@edpaget
Copy link
Contributor Author

edpaget commented Oct 20, 2014

Given #206 it seems like we should just stick with PaperTrail.

@edpaget edpaget closed this as completed Oct 20, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@edpaget @camallen