Hey,
Zitan Broth wrote:
>Btw, not sure how svn currently handles it, but when we were looking at
>virtual directories we decided only to store text files *in* the database,
>and leave everything else on the server. The DB effectively *knows* where
>everything is (holding all the live props), but the app layer puts the dead
>props resource requests together. Or perhaps you were thinking of just
>using an sql db for the repository library .... I can wait for the doc of
>course :-)
>
>
Well, the doc that is coming has nothing to do with SQL other than I
need to make the pluggable changes first so I can co-exist with the BDB
FS. The idea is that other folks can have a go at doing it *their* way.
I can tell you I'm not a huge fan of storing *anything* outside the DB.
Performance issues associated with raw and/or LOBs can usually be dealt
with in other ways.
I did write a quick SQL design sorta thingy a while back:
http://www.cdrguys.com/subversion/sql_fs_docs/svn_fs_sql.htm. It was
based on the http://www.cdrguys.com/subversion/fs_refactoring/index.htm
work. The refactoring document is what I'm re-documenting. The SQL
document will be improved later.
If you haven't read "subversion/libsvn_fs/structure", you need to. It's
required reading for anyone interested in the FS. Also read the
comments in "subversion/include/svn_fs.h". For starters;-) It should
give you an idea of what has to be implemented. The first SQL
implementation will leverage as much of the existing logic as possible.
gat
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 29 17:55:28 2003