Somebody in this thread said that files don't belong in a db, and proposed to only put the metadata in the db. That argument seems misguided to me: when recovering the db and filesystem after a host crash, you'd have to go to extra hoops to make sure the metadata matches the filesystem data. Note that Perforce puts everything in a database and it's rock solid. The main problems I had with svn's use of Berkeley DB were packaging issues (but then, I was using a pre-1.0 beta of svn) and poor management of the Berkeley DB by the svn code, requiring frequent db "recovery" actions; also a bug that caused accesses by different users to hose the database in a subtle way. All of that seems fixable. -- --Guido van Rossum (home page: http://www.python.org/~guido/) Ask me about gmail.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4