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

Strange ACTUAL_NODE record

From: Branko Čibej <brane_at_wandisco.com>
Date: Sun, 06 Apr 2014 14:33:51 -0600

I have the immense privilege to be able to debug a wc.db that was
upgraded to the 1.8 format using our code from a 1.7 format created by
SVNKit. It's mostly plain sailing, but on this happy occasion I'm seeing
a rather strange record in the database, both before and after the upgrade:

$ sqlite3 wc.db
SQLite version 2014-03-11 15:27:36
Enter ".help" for usage hints.
sqlite> .nullvalue "(nul)"
sqlite> SELECT * FFROM NODES WHERE local_relpath = "dir/file";
1|dir/file|0|DisplayServer|1|trunk/dir/file|5796|normal|(nul)|(nul)|file|(svn:keywords 23 Author Date Id Revision svn:eol-style CRLF)|(nul)|$sha1$d4f0f7a37ff21bb3d1ce58ed5906b93351d7c87c|(nul)|4832|1338401677262718|theauthor|1032|1338550831496845|(nul)|(nul)|(nul)

The thing I don't understand is: how can we have an ACTUAL_NODE record
with all the flags nulled out, and an op_depth=0 record in NODES at the
same time?

Note that the record first appeared in the wc.db created by SVNKit, but
our WC upgrade left it untouched. Unfortunately I have only the wc.db
files, not the whole working copy.

-- Brane

Branko Čibej | Director of Subversion
WANdisco // Non-Stop Data
e. brane_at_wandisco.com
Received on 2014-04-06 22:34:30 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.