On Fri, Mar 13, 2009 at 8:15 AM, Hyrum K. Wright
<hyrum_wright_at_mail.utexas.edu> wrote:
> On Mar 12, 2009, at 6:34 PM, Greg Stein wrote:
...
>> When you write properties, then you've got a whole different issue.
>> Those always go into ACTUAL, but props might not be there (yet). So
>> you may have to INSERT a copy of them. Or maybe a row exists, so you
>> need to UPDATE the props column to create an initial value. That
>> initial value comes form WORKING or from BASE. Then, after the copy,
>> you can update props in ACTUAL.
>
> Okay, that makes sense, and I'll update svn_wc__db_op_set_props()
> accordingly. I presume that svn_wc__db_op_set_prop() just does the
> same thing, but replaces the given prop, such as is already happening.
"INSERT OR REPLACE" syntax might be helpful for implementation here.
http://www.sqlite.org/lang_replace.html
http://www.sqlite.org/lang_insert.html
>> Of course, if there are props in ACTUAL, and somebody tries to add a
>> row to WORKING, then you've got a conflict: those props are against
>> BASE, but somebody is trying to alter that. You essentially have
>> "local mods".
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1317662
Received on 2009-03-13 16:31:05 CET