Barry,
I have little to say on the SQL is good or bad, however, PostGres exports
a C/C++ API that maps long objects to an API that walks and talks like
open/read/write/close/stat/seek from UNIX.
See this documentation:
http://www7.us.postgresql.org/users-lounge/docs/7.1/programmer/lo-interfaces.html
From the a SQL commandline it is hard to get it to ship the data over the
network directly, but it is easy to get it in and out programmatically.
I stopped using it around 7.02 or so, so I might be a bit dated.
From the description of how Subversion is supposed to work, I would
assume that this API being close that the API I thought SubVersion tried
to emulate that it would be simple.
One small note, In the past, I have used Large Object under PostGres in a
production environment, and unless they have gotten an order of
magnitude faster they are too slow when there are large numbers of them.
I know they were slated for a big round of re-implementation in the
version or two after I stopped using it. I don't know if they are
faster or not. Worry about all this information after v1.0 from the
posts on the lists.
Thanks,
Kirby
Barry Scott wrote:
> I'm well aware of OODB technology. I have worked on Versant and
> Objectivity as well relational DB PostgreSql and SQL Server.
>
> My primary concern is getting a serious database and query capability.
>
> Why do you think that a relational database would be a problem?
>
> I can think of reasons like quality of BLOB support that might make it
> harder to use certain DB. (e.g. PostgreSQL BLOB is to and from local
> disk on the DB server not the disk of the client.)
>
> BArry
>
>
> -----Original Message-----
> From: Marcus Comstedt [mailto:marcus@mc.pp.se]
> Sent: 27 January 2002 13:57
> To: dev@subversion.tigris.org
> Subject: RE: First impressions...
>
>
>
> Barry Scott <barry.alan.scott@ntlworld.com> wrote:
>
>
>>Using a database is far more powerful then using a file system.
>>
>>Being able to use SQL to query the repository is a good solution
>>to building the more complex SCM solutions on top of SVN.
>>
>>My guess would be that folks that want the database backends
>>have tackled complex SCM problems and know why the simple interfaces
>>to meta data have problems. Speed of query across large sets of
>>versions and files being one.
>>
>
> Don't make the mistake of puting an == between "SQL" and "database".
> SQL implies a _relational_ database, which I think is totally out of
> place here. A hierarchical or object database seems far more
> appropriate.
>
>
> // Marcus
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:05 2006