Interesting project but I don't think it's going to help in this case, the replicate gem provides a nice way to transport a record (and it's associated data) from one database to another. I get the feeling I would still hit the same problem when it comes to loading and reporting on the stored data.
To use replicate I would need to create the database records from a snapshot, report on them and then delete them which I don't think is a very good solution. Nice gem though, I may just use it for something else I have in mind. - Scott On Tuesday, 9 July 2013 16:45:16 UTC+10, Paul Annesley wrote: > > This is a long shot, but maybe this would be a good alternative to your > JSON store implementation? > https://github.com/rtomayko/replicate > > > > On Tue, Jul 9, 2013 at 4:33 PM, Scott Harvey > <[email protected]<javascript:> > > wrote: > >> So it's been over a year and a half since I posted this question and it's >> now time time for me to actually implement this feature. >> >> The past few days I've played around generating a large JSON string and >> saving it to the database as a way of taking a snapshot of a project. >> >> Generating and saving the JSON string worked well and I can even use that >> string to build a new project along with it's associated records. >> >> The problems start when I try to walk through the associations to >> generate reporting numbers. >> >> I'm using the snapshot to build a new project, and it's associated >> records, in memory but when walking the associations sometimes ActiveRecord >> will hit the database rather than use the objects in memory. >> >> So basically I'm still on the hunt for a good way to solve this problem, >> has anyone had any recent experience trying to tackle this issue? >> >> - Scott >> >> On Wednesday, 28 September 2011 17:23:59 UTC+10, Scott Harvey wrote: >>> >>> Hey everyone, >>> >>> I'm working on the reporting section of an application at the moment and >>> we are trying to determine the best way to take snapshots of a project >>> during it's lifecycle. >>> >>> Along with the project model itself there are another 10 or so >>> associated models that would need to be versioned as well. >>> >>> I've looked into the paper trails and vestal versions gems and both seem >>> to have almost everything I need except a way to store and retrieve complex >>> associations. >>> >>> Anyone have any suggestions on how to version complex associations >>> within Rails? >>> >>> - Scott >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ruby or Rails Oceania" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> >> To post to this group, send email to [email protected]<javascript:> >> . >> Visit this group at http://groups.google.com/group/rails-oceania. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/rails-oceania. For more options, visit https://groups.google.com/groups/opt_out.
