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

Re: backing up a repository over a network

From: William Uther <willu_at_cse.unsw.edu.au>
Date: 2003-06-10 05:14:08 CEST

On Tuesday, June 10, 2003, at 11:55 AM, Ben Collins wrote:

> On Mon, Jun 09, 2003 at 10:43:51PM -0400, Greg Hudson wrote:
>> On Mon, 2003-06-09 at 15:51, cmpilato@collab.net wrote:
>>> I don't really understand the "svn unawareness" issue. Files are
>>> files, right? Binary data. Ones and zeros. Now, granted, if you
>>> move a Berkeley DB environment between some platforms, things'll be
>>> all busted up. That's why Berkeley provides its own db_dump and
>>> db_load utilities, to take care of endianness issues between
>>> platforms.
>> Not according to the docs:
>> http://www.sleepycat.com/docs/ref/am_conf/byteorder.html
> From personal experience, I think this is bogus info. I've never been
> able to transfer bdb databases between endian-different machines.

 From the above quoted link (in bold at the bottom):
> It is important to note that the Berkeley DB access methods do no data
> conversion for application specified data. Key/data pairs written on
> a little-endian format architecture will be returned to the
> application exactly as they were written when retrieved on a
> big-endian format architecture.

The DB format itself is labelled with the endianness it was created
with, and so can be moved. Any data you put into the database is not
automatically converted.

Will :-}

Dr William Uther                            National ICT Australia
Phone: +61 2 9385 6926             School of Computer Science and 
Email: willu@cse.unsw.edu.au             University of New South Wales
Jabber: willu@jabber.cse.unsw.edu.au          Sydney, Australia
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 10 05:14:58 2003

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.