revision

I've read all the SO questions, the Coding Horror articles, and Googled my brains off searching for the best ways to revision control data. They all work and they all have their appropriate implementations based on use cases and so on. What I really want to know is why hasn't a database been written to natively support revisioning on the data-level? What I am baffled with is that the API is already practically in place with transactions. We start a transaction, change some data, and commit . We are authenticating against the database too so blame is present. My company stores end of month

I need to store RDF triples, while keeping track of modifications. Is there anything out there for this service? Alternatively, how would you keep track of revision while using a context-aware triplestore ? Edit : please note that I don't need only the changeset. I also need to see the triples at any time in the past. I tried to address this sort of thing by storing additional triples describing who said what, when. But you need reification, named graphs, or quads which can ruin decidability. in addition to the other answers, also take a look at the Lensfield system (research software at the

I'm having problems understanding how I to use dynamic revisions of Ivy effectively in my Java projects. Currently, I have the following layout: lib-a revision: 1.0.0 status: release dependencies: none lib-b revision: 2.0.0 status: release dependencies: lib-a, rev 1.0.0 project-a revision: 3.0.0 status: release dependencies: lib-b, rev 2.0.0 project-b revision: 4.0.0 status: release dependencies: lib-b, rev 2.0.0 That means I always keep the status to release and use explicit version numbers. If I would change lib-a during development, say lib-a , this is quite painful. I save the changes in

Near as I can tell, CouchDB revisions are not to be treated like revisions in the document versioning sense of the word. From glancing at other posts, they seem to be regarded as transient data that exists until a coarse-grained compact operation is called. My question is, if I am interested in using CouchDB to maintain documents, as well as a version-history of those documents, should I allow that to be handled natively by CouchDB revisions, or should I build a layer on-top that will survive a compact operation? I am thinking the latter, simply because Couch does not replicate revisions of

Is there any API to get wikipedia revision id by date, instead of checking all the revision history and extract out the most recent revision before that date? Thank you! Bergi The revision query api allows you to pass timestamps to get only revisions from a specified interval. Use api.php?action=query&prop=revisions&rvlimit=1&rvstart= myTimestamp Check out the Manual:WfTimestamp for accepted formats - yyyymmddhhmmss always works. Building on the previous answer: The always accepted format yyyymmddhhmmss returned errors. This example returned a valid response: JSON XML The id in field revid

Is it possible to checkout only those files from a SVN repository that were modified in a revision or range of revisions, without checking out any files that were not modified? My suggestion is in the same lines as flolo suggests. But, takes a range. You could the following shell function. function checkout_files_in_revrange() { svn_url=$1; start_rev=$2; end_rev=$3; for theCheckoutCanditate in `svn log -r $start_rev:$end_rev --verbose --incremental | grep " M " | cut -f5 -d' ' | cut -f3- -d/` do svn co $svn_url/$theCheckoutCandidate -q; done } There is afaik now direct way to get just the