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

Re: svn commit: r39580 - trunk/subversion/libsvn_wc

From: Greg Stein <gstein_at_gmail.com>
Date: Thu, 24 Sep 2009 21:11:09 -0400

On Thu, Sep 24, 2009 at 20:21, Hyrum K. Wright <hyrum_at_hyrumwright.org> wrote:
> On Sep 24, 2009, at 5:04 PM, Bert Huijben wrote:
>> Author: rhuijben
>> Date: Thu Sep 24 14:04:20 2009
>> New Revision: 39580
>> Log:
>> Update the WC metadata schema to reflect the new idea about storing
>> conflicts. We will store all conflicts in a TEXT field of the
>> table serialialized via the skel api.
> Forgive me for being dense, but why are we using skels here?  Why
> should we worry about serialization when a structured format (which is
> what SQL is meant to be) does that for us?

Same reason we serialize properties: we probably don't need the pieces
of data available for manipulation/query individually, and a skel can
be easier to deal with when 1:N mappings exist (one node, N prop
conflicts) and we want *all* N all the time.

We *could* have a prop_conflict_data for that last 1:N element, but we
still don't really need separable access to the other data items. (or,
at least that's my impression)


Received on 2009-09-25 03:11:18 CEST

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.