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

Re: minimalist example of svn_txdelta_run?

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Thu, 31 Mar 2011 19:33:43 +0200

Clifford Yapp wrote on Thu, Mar 31, 2011 at 08:50:37 -0400:
> On Thu, Mar 31, 2011 at 12:02 AM, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
>
> > Typically to update a file in the repository using the svn_delta API
> > you'd already know the current contents of that file.  Is that the case
> > for you?
> >
> > What are you trying to do?  Can you give an example with sample data?
>
> Well, what I was trying to do in my test case was take a file in a
> repository with content "test string 1", and update its content to
> "test string 2" using mechanisms that would confirm there is a
> difference between those two strings before updating the file to the
> new string - basically the simplest possible situation.
>

Okay, that sounds right. (Depending on your scenario, I guess you might
be able to skip the check and go directly to attempting the commit.)

I'll reply to your other mail in a second.

> The "real" problem I'm trying to solve is this - I have binary data
> stored in lots of small files in a subversion repository (serialized
> geometry data). I have as incoming data the serialized binary data
> for one of the objects. I want to commit the new contents from the
> incoming object to the repository, if that incoming data is different
> from the version that is already in the repository. All of this is
> in-memory, no filesystem files are involved except what the FSFS
> backend is doing internally.
>
> Cheers,
> CY
Received on 2011-03-31 19:34:27 CEST

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

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