blocks|key|3293345|text|几个月前，我测试了几个解决方案，vestal_versions是最有效的。还有一个来自Ryan+Bates的great+screencast+here。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3293346|如果您正在寻找其他替代方案，请查看The+Ruby+Toolbox+list。|3293347|entityMap|0|LINK|mutability|MUTABLE|url|http://railscasts.com/episodes/177-model-versioning|1|https://www.ruby-toolbox.com/categories/Active_Record_Versioning^0|G|F|1I|L|0|0|H|L|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@$9|U|A|V|1|W]]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@$9|Y|A|Z|1|10]]|E|$]]|$1|H|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]|P|$5|K|L|M|E|$N|Q]]]]

A couple of months ago I tested a couple of solutions and <code>vestal_versions</code> was the most effective.
There's also a <a href="http://railscasts.com/episodes/177-model-versioning" rel="nofollow noreferrer">great screencast here</a> from Ryan Bates.

If you are looking for other alternatives, check out <a href="https://www.ruby-toolbox.com/categories/Active_Record_Versioning" rel="nofollow noreferrer">The Ruby Toolbox list</a>.

blocks|key|325636|text|我们在一个项目中使用了acts_as_audited，并取得了相当好的成功。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|325637|你可以在http://github.com/collectiveidea/acts_as_audited/上找到它|offset|length|325638|(上次提交时间:11月:-)|325639|entityMap|0|LINK|mutability|MUTABLE|url|http://github.com/collectiveidea/acts_as_audited/^0|0|4|1D|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

We used acts_as_audited in a project, with quite a good success.

You can find that at <a href="http://github.com/collectiveidea/acts_as_audited/" rel="nofollow noreferrer">http://github.com/collectiveidea/acts_as_audited/</a>

(last commit in november :-) )

blocks|key|3079999|text|我上周使用过vestal_versions，是的，它是最先进的替代方案，至少在空间方面是这样:你只需要存储你真正需要的东西。这是一个活跃的项目，1.0版将是一个巨大的更新，有许多新功能；看看1.0分支就知道我的意思了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3080000|但在尝试了一下之后，我注意到了一个很大的缺陷:性能。每次你需要一个特定的版本时，你必须遍历所有中间版本，重新构建你需要的版本。这也意味着你不能直接编辑或删除一个版本，因为它可能会弄乱修改，破坏链条。要做到这一点，您需要充分处理版本，而vestal_versions目前还不能做到这一点。|3080001|这样，对于我遇到的问题，我最终得到了我自己的版本控制解决方案。我需要性能和快速删除和编辑版本的能力，所以我牺牲了存储空间，开发了类似于act_as_versioned的东西。|3080002|但是，如果你不需要这样做，并且不需要频繁地恢复，我强烈推荐vestal_versions。这是一个先进的、可靠的解决方案，也是一个积极的解决方案，背后有一位充满激情的开发人员。|3080003|entityMap^0|6|F|0|39|F|0|1V|G|0|T|F|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|L|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|M|$]]

I've worked with <code>vestal_versions</code> last week and yes, it is the most advanced alternative, at least in terms of space: you store just what you really need. It is an active project and the version 1.0 is going to be a huge update with many new features; just look at the 1.0 branch to know what I mean.

But after playing with it a bit, I've noticed a big flaw: performance. Every time you need an specific version, you have to go through all intermediate ones, reconstructing the version you need. This also means you cannot edit or delete a version directly, because it can mess with modifications, broking the chain. For do this, you need to process versions adequately, what <code>vestal_versions</code> currently does not do.

This way, for the problem I had, I ended up with my own versioning solution. I needed performance and the ability to delete and edit versions rapidly, so I sacrificed storage and developed something similiar to <code>act_as_versioned</code>.

BUT, if you don't need this and do not have to revert very frequently, I highly recommend <code>vestal_versions</code>. It is an advanced, solid solution and an active one, with a passionate developer behind it.

blocks|key|323944|text|我一直在使用一个名为"paper_trail“的宝石。这似乎是目前网上最好的解决方案。它集审计和版本控制于一体。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|323945|http://github.com/airblade/paper_trail|offset|length|323946|希望这能有所帮助！|323947|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|12|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@$D|Q|E|R|1|S]]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]]]

Ive been working with a gem called "paper_trail". It seems to be the best solution online at the moment. It has auditing and version control in one. 

<a href="http://github.com/airblade/paper_trail" rel="noreferrer">http://github.com/airblade/paper_trail</a>

Hope this helps!

blocks|key|3293435|text|嘿，我想知道有没有人想过在后台使用Perforce、GitHub等来代替数据库来支持版本控制？所以它本质上是基于文件的数据检索，我猜...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3293436|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Hey, I'm wondering if anyone has thought of using Perforce, GitHub, etc. on the backend INSTEAD of a database as a way to support versioning? So it would essentially be file-based retrieval of data, I guess...

blocks|key|3293444|text|另一个插件是paper_trail。以下是今天发布的铁路广播的链接：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3293445|http://railscasts.com/episodes/255-undo-with-paper-trail|offset|length|3293446|他还提到了为什么他更喜欢paper_trail而不是vestal_versions|3293447|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1K|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@$D|Q|E|R|1|S]]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]]]

Another plugin is paper_trail. Here is a link to the railscasts posted today:

<a href="http://railscasts.com/episodes/255-undo-with-paper-trail" rel="nofollow">http://railscasts.com/episodes/255-undo-with-paper-trail</a>

He also mentions why he prefers paper_trail over vestal_versions

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:

<ul>
<li><code>acts_as_versioned</code></li>
<li><code>simply_versioned</code></li>
<li><code>vestal_versions</code></li>
</ul>

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, <code>acts_as_versioned</code> 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?

Versioning of Models in Ruby on Rails

我正在寻找一个插件/act来允许我的模型的版本控制。很难找到可用的解决方案的列表。到目前为止，我得到了以下结论：acts_as_versionedsimply_versionedvestal_versions后两种解决方案只需要一个版本表--这听起来不错，但我有一种不好的预感，即迁移的简易性将如何受此影响(因为它们将状...

问Ruby on Rails中的模型版本控制
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Ruby on Rails中的模型版本控制EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Ruby on Rails中的模型版本控制
EN