vestal-versions | 易学教程

Versioned associations using vestal_versions?

阅读更多关于 Versioned associations using vestal_versions?

问题 I'd like to be sure if vestal_versions does support versioned associations (it seems like it doesn't) before switching out to another versioning gem that can support versioned associations e.g => has_versioning. I haven't looked at the code yet but I couldn't find anything related with versioned associations from the readme file or the issue section on github. Help would be appreciated! 回答1: (At the moment of writing this) There is an associations branch in the official vestal_versions

Rails 3.2 app - Should I use a versioning gem (paper_trail or vestal_versions) or handle it manually?

阅读更多关于 Rails 3.2 app - Should I use a versioning gem (paper_trail or vestal_versions) or handle it manually?

问题 My question: Should I roll my own model versioning or use one of the versioning gems that's already out there? If I should use a gem, which one seems best for this application? Info about my app My app is a simple Checklist app. There are Checklists and Jobs, and I track user responses with Responses and Submissions. The Response tells me what the use said ("Done", with a note "We need more mops.") and the Submission tells me when that particular Checklist was filled out (because there may be

Versioning of Models in Ruby on Rails

阅读更多关于 Versioning of Models in Ruby on Rails

问题 I'm looking for a plugin/act to allow versioning of my models. It's kind of difficult to find a list of the available solutions. So far I gathered: acts_as_versioned simply_versioned vestal_versions The last two solutions only require a single version table - this sounds nice, but I've got a bad feeling about how the ease of migrations will be affacted by this (because they serialize states as a string). On the other hand, acts_as_versioned is a little bit dusty (last commit in January). Are

how to insert user_id,user_name,user_type with vestal versions?

阅读更多关于 how to insert user_id,user_name,user_type with vestal versions?

问题 how to insert user_id,user_name,user_type with vestal versions into the versions table ? class Page < ActiveRecord::Base versioned end 回答1: You need to add a field to your versioned model, :updated_by, then the plugin will do the rest. So for example, @page.update_attributes(:body => "some cool content", :updated_by => current_user) 来源： https://stackoverflow.com/questions/5778088/how-to-insert-user-id-user-name-user-type-with-vestal-versions

Rails 3.2 app - Should I use a versioning gem (paper_trail or vestal_versions) or handle it manually?

阅读更多关于 Rails 3.2 app - Should I use a versioning gem (paper_trail or vestal_versions) or handle it manually?

My question: Should I roll my own model versioning or use one of the versioning gems that's already out there? If I should use a gem, which one seems best for this application? Info about my app My app is a simple Checklist app. There are Checklists and Jobs, and I track user responses with Responses and Submissions. The Response tells me what the use said ("Done", with a note "We need more mops.") and the Submission tells me when that particular Checklist was filled out (because there may be many submissions and sets of responses for a given checklist). I'll show my associations below, in

Versioning of Models in Ruby on Rails

阅读更多关于 Versioning of Models in Ruby on Rails

I'm looking for a plugin/act to allow versioning of my models. It's kind of difficult to find a list of the available solutions. So far I gathered: acts_as_versioned simply_versioned vestal_versions The last two solutions only require a single version table - this sounds nice, but I've got a bad feeling about how the ease of migrations will be affacted by this (because they serialize states as a string). On the other hand, acts_as_versioned is a little bit dusty (last commit in January). Are there any recent experiences with any of these? Or other solutions (or forks) I might have overlooked?