You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Greg Stein <gs...@lyra.org> on 2003/05/01 01:13:50 UTC

Re: DASL and pluggable-db

Hey Elias... small world :-)

On Wed, Apr 30, 2003 at 11:17:36AM -0700, Elias Sinderson wrote:
>...
> Glen Thompson mentions the issue of providing a pluggable DB layer 
> before addressing DASL-like functionality. I'm curious as to the reason 
> Glen feels this way - is there a compelling architectural reason for 
> this?

I think the simplest answer is that Berkeley DB is not very good at
responding to the kinds of queries that DASL can/would generate. In fact,
with BDB, you pretty much have to have defined ahead-of-time the kind of
queries you need to make, and then you design the database(s) around that.

Thus, moving to a SQL database with its greater query flexibility is pretty
much a first step before you can consider DASL types of functionality.

[ note that I'm mostly talking about property-based queries here; I imagine
  a text/content-based query would be about the same on any backend database
  since those queries are usually handled by complicated indexing systems
  rather than the core database ]

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: DASL and pluggable-db

Posted by "Glenn A. Thompson" <gt...@cdr.net>.
> 
>
>I think the simplest answer is that Berkeley DB is not very good at
>responding to the kinds of queries that DASL can/would generate. In fact,
>with BDB, you pretty much have to have defined ahead-of-time the kind of
>queries you need to make, and then you design the database(s) around that.
>
>Thus, moving to a SQL database with its greater query flexibility is pretty
>much a first step before you can consider DASL types of functionality.
>  
>
Yeah that too:-)

gat


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org