4 ms·
tghw's interpretation is closer to being correct. A Veracity repo can have lots of DAGs (directed acyclic graphs). A DAG in a repo can either be a "tree dag"
by ericsink 16y ago
tghw's interpretation is closer to being correct.
A Veracity repo can have lots of DAGs (directed acyclic graphs).
A DAG in a repo can either be a "tree dag" or a "database dag".
Veracity's notion of a "database" is a model that is unique to Veracity, although its concepts are quite common. Records. Fields. Multiple record types. Simple constraints. Links between records. Simple queries. It's not SQL.
Nothing here implies that Veracity will help you, as a database developer on SQL Server or Oracle, manage the versioning of your schema and sprocs and so on. Those are interesting features, but they're distinct from (and a lot higher level than) the stuff I was describing.
- ojilles 16y agoThanks for clarifying!
- igravious 16y agoHi Eric, love your ambitions. Why did you feel the need to put something so database-y right into the repo and go beyond file/directory versioning and key,value tags?
- qaexl 16y agoI am very interested in that "database dag". If it works the way I think it does, I think it will be far more significant than the source control part of the product. For example, I'd like to be able to put together a decentralized knowledge base. Who knows, we may see http://redmonk.com/sogrady/2010/05/04/open-data-github/ http://redmonk.com/sogrady/2010/05/04/open-data-github/ sooner than later.