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

Re: DB Lib in Client(was Re: static linking RA libs)

From: Kevin Pilch-Bisson <kevin_at_pilch-bisson.net>
Date: 2001-02-17 02:16:57 CET

On Fri, Feb 16, 2001 at 03:49:23PM -0800, Greg Stein wrote:
> On Fri, Feb 16, 2001 at 06:24:11PM -0500, Greg Hudson wrote:
> If we don't make SVN define a DBM style for APRUTIL, then yes: we could
> potentially run into situations like the above. I'm not sure it is our
> fault, though. On my RH system, DB2 is the right choice; it just comes
> standard. Only when I want to have a portable working dir, do I begin to
> care. And note that *no* DBM has portable byte-ordering (that I know of). If
> you used the working copy between a Sparc and an x86, you're just flat out
> screwed.
> [ and no: apr_dbm has no auto-detection or dynamic selection at this time;
> excellent feature request which I had thought of, but not there now. I was
> thinking about it to detect SDBM dbs that were compiled with different
> record size limits. ]
> > For the wc, we should either restrict ourselves to the lowest common
> > denominator of functionality, or make the highest common denominator a
> > hard requirement. Making the wc data format dependent on compile-time
> > options is a recipe for disaster.
> I'd take the LCD over anything more (and as pointed out, it should be fine
> for us anyways). Not sure that I entirely agree with the second sentence,
> but no matter.
> > (Especially since we've made a number of design decisions based on the
> > requirement of being able to take a wc subdirectory, move it from one
> > place to another and back, and have it still work the whole time.)
> Well... I'm not sure about "how far". Surely, move it around within a
> filesystem on one machine. I never knew we planned to allow them to be truly
> portable across systems; certainly not a requirement in my head.

Just thinking that an alternate, or maybe addition to the stuff above is
to allow the builder to specify a db library, but also write import
export functionality for the different DB types. That way a wc could
be migrated to a newer, faster db, but wouldn't necessarily always work
if it was just plunked down in another place.

This is just an idea though. Personally I still prefer the plain old
ascii text files, and can't see them not being sufficient. (As numerous
people have stated I beleive).

Kevin Pilch-Bisson                    http://www.pilch-bisson.net
     "Historically speaking, the presences of wheels in Unix
     has never precluded their reinvention." - Larry Wall

  • application/pgp-signature attachment: stored
Received on Sat Oct 21 14:36:22 2006

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.