|
Does Veracity truly have the ability to version database data, as this InfoQ article indicates? If so, how? The ability to version data from arbitrary databases could be a revolutionary feature, and I'm eager to try it. |
|
If you mean "can I point Veracity at my SQL/NoSQL/etc. database and have that magically versioned?", then no. We don't do that. What the article was discussing was the distributed, extensible, versioned and auto-merged database layer on which Veracity is built. It's what allows us to have truly distributed bug tracking, for example. And it is extensible, with new data and behaviors added by the user -- the wiki module, for instance, drops in via database templates, javascript and HTML. All this data lives within Veracity's framework, however; the goal is to provide extensible means to manage, version and share your team's information. |
