Hey:
>
> As for the SQL backend, it would be good if the same instance of the DB could
> be used for all repos on the server, either on or many, if it can be setup to
> do so.
By instance I assume you mean it in the executable sense. My first thought is to
make each repos a schema/user in Oracle. In MySql I think they will have to be
separate DBs but multiple DBs can be served by one mysqld. Other DBs I'm sure can
accommodate this as well.
It should allow for 1 to n instances. Whats important is that the table names
don't collide and that repos getting beaten to death can be easily moved to another
instance if needed. I really want to hide the instance detail behind some sort of
connection URL like is used by JDDC and DBI. "svnadmin create" a little tricky as
it will require more input than a simple URL. I'm betting there is some sort of
XML standard for DDL but I haven't checked yet. But it's too soon to worry about
those details. Right now I'm focused on how to Slide SQL into the mix without
impacting the current development too much.
I don't want to have my work punted to post 1.0 if I can avoid it.
gat
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 2 05:34:44 2002