[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SQL Support

From: John Peacock <jpeacock_at_rowman.com>
Date: 2005-04-17 16:30:03 CEST

Lester Caine wrote:
> Is any progress being made on SQL support, or am I restricted to FSFS
> for the time being?

Not right now and yes (respectively). The core development thrust for 1.2 has
been support for locking (just like FSFS was the dominant issue for 1.1). I
doubt SQL will be a prominent issue for a while (I think true renames/moves is
up next, but I'm not a core developer and just basing that on what seems to be
the itch that needs scratching the most).

>
> How 'integrated' is the Berkeley DB API - would it be that difficult to
> switch to another engine with - as I see it - all of Berkeleys
> capabilities and more ( we run Win98SE slave databases on many 24/7
> sites ;) )

BDB is highly integrated; FSFS was a completely new implementation, which may be
useful as a path towards an eventual SQL backend. You can see notes/sql-backend
for some pre-FSFS discussion of the issues involved in creating a generic SQL
abstraction layer. There's also some propaganda about FSFS in notes/fsfs that
you might find useful.

Win98 is not a supported platform (in the sense that there are things that don't
work and are not viewed as important to fix because the platform has long since
been abandoned by the vendor). See the list archive for more details.

HTH

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 17 16:26:50 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.