Re: [Monotone-devel] Problems with the tutorial

[Thomas Keller]

Am 02.02.2010 16:16, schrieb Gary:
> On Tue, Feb 02, 2010 at 04:03:53PM +0100, Thomas Keller wrote:
> 
>> can you please run
>> the commit command with --debug and post the output of that?
> 
> $ mtn commit --debug --message="initial checkin of tutorial"
> [...]
> mtn: getting heads of branch mimosa.ex2.5
> mtn: prepared statement SELECT revision_id FROM revision_certs WHERE name = ? 
> AND value = ?
> mtn: binding 2 parameters for SELECT revision_id FROM revision_certs WHERE 
> name = ? AND value = ?
> mtn: binding 1 with value 'branch'
> mtn: binding 2 with value '6d696d6f73612e6578322e35'
> mtn: found heads of branch mimosa.ex2.5 (0 heads)
> mtn: prepared statement BEGIN EXCLUSIVE
> mtn: binding 0 parameters for BEGIN EXCLUSIVE
> mtn: prepared statement SELECT id FROM revisions WHERE id = ?
> mtn: binding 1 parameters for SELECT id FROM revisions WHERE id = ?
> mtn: binding 1 with value 'fdbb055cab4431949263543644cb13f6cb65dc63'
> mtn: inserting new revision fdbb055cab4431949263543644cb13f6cb65dc63
> mtn: inserting full version f6996ce2dfc5d32bda8b574c3e9ce75db8d55492
> mtn: prepared statement SELECT 1 FROM file_deltas WHERE id = ? LIMIT 1
> mtn: binding 1 parameters for SELECT 1 FROM file_deltas WHERE id = ? LIMIT 1
> mtn: binding 1 with value 'f6996ce2dfc5d32bda8b574c3e9ce75db8d55492'
> mtn: prepared statement SELECT 1 FROM files WHERE id = ? LIMIT 1
> mtn: binding 1 parameters for SELECT 1 FROM files WHERE id = ? LIMIT 1
> mtn: binding 1 with value 'f6996ce2dfc5d32bda8b574c3e9ce75db8d55492'
> mtn: inserting full version 6c3e19be4d8aebb7584e94335ada80b2c0f6d997
> mtn: binding 1 parameters for SELECT 1 FROM file_deltas WHERE id = ? LIMIT 1
> mtn: binding 1 with value '6c3e19be4d8aebb7584e94335ada80b2c0f6d997'
> mtn: binding 1 parameters for SELECT 1 FROM files WHERE id = ? LIMIT 1
> mtn: binding 1 with value '6c3e19be4d8aebb7584e94335ada80b2c0f6d997'
> mtn: inserting full version ad88bbbb1b7507ddff26be67efd91d95e069afb6
> mtn: binding 1 parameters for SELECT 1 FROM file_deltas WHERE id = ? LIMIT 1
> mtn: binding 1 with value 'ad88bbbb1b7507ddff26be67efd91d95e069afb6'
> mtn: binding 1 parameters for SELECT 1 FROM files WHERE id = ? LIMIT 1
> mtn: binding 1 with value 'ad88bbbb1b7507ddff26be67efd91d95e069afb6'
> mtn: binding 1 parameters for SELECT id FROM revisions WHERE id = ?
> mtn: binding 1 with value 'fdbb055cab4431949263543644cb13f6cb65dc63'
> mtn: binding 1 parameters for SELECT 1 FROM file_deltas WHERE id = ? LIMIT 1
> mtn: binding 1 with value 'f6996ce2dfc5d32bda8b574c3e9ce75db8d55492'
> mtn: binding 1 parameters for SELECT 1 FROM file_deltas WHERE id = ? LIMIT 1
> mtn: binding 1 with value '6c3e19be4d8aebb7584e94335ada80b2c0f6d997'
> mtn: binding 1 parameters for SELECT 1 FROM file_deltas WHERE id = ? LIMIT 1
> mtn: binding 1 with value 'ad88bbbb1b7507ddff26be67efd91d95e069afb6'
> mtn: prepared statement INSERT INTO revisions VALUES(?, ?)
> mtn: binding 2 parameters for INSERT INTO revisions VALUES(?, ?)
> mtn: binding 1 with value 'fdbb055cab4431949263543644cb13f6cb65dc63'
> mtn: binding 2 with value '1f8b08000000000000ff65d06b6ac3300c00e0ff3e45c801..'
> mtn: prepared statement INSERT INTO revision_ancestry VALUES(?, ?)
> mtn: binding 2 parameters for INSERT INTO revision_ancestry VALUES(?, ?)
> mtn: binding 1 with value ''
> mtn: binding 2 with value 'fdbb055cab4431949263543644cb13f6cb65dc63'
> mtn: prepared statement SELECT 1 FROM roster_deltas WHERE id = ? LIMIT 1
> mtn: binding 1 parameters for SELECT 1 FROM roster_deltas WHERE id = ? LIMIT 1
> mtn: binding 1 with value 'fdbb055cab4431949263543644cb13f6cb65dc63'
> mtn: prepared statement SELECT 1 FROM rosters WHERE id = ? LIMIT 1
> mtn: binding 1 parameters for SELECT 1 FROM rosters WHERE id = ? LIMIT 1
> mtn: binding 1 with value 'fdbb055cab4431949263543644cb13f6cb65dc63'
> mtn: prepared statement SELECT node FROM next_roster_node_number
> mtn: binding 0 parameters for SELECT node FROM next_roster_node_number
> mtn: prepared statement INSERT INTO next_roster_node_number VALUES(1)
> mtn: binding 0 parameters for INSERT INTO next_roster_node_number VALUES(1)
> mtn: binding 0 parameters for SELECT node FROM next_roster_node_number
> mtn: prepared statement UPDATE next_roster_node_number SET node = ?
> mtn: binding 1 parameters for UPDATE next_roster_node_number SET node = ?
> mtn: binding 1 with value '2'
> mtn: sqlite error: 1: SQL logic error or missing database

I'm not sure why the SQL update on next_roster_node_number should fail -
given the fact that a previous INSERT worked - Stephe, Lapo, could you
please have a look at it? I'm clueless...

Thomas.

-- 
GPG-Key 0x160D1092 | address@hidden | http://thomaskeller.biz
Please note that according to the EU law on data retention, information
on every electronic information exchange might be retained for a period
of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en

signature.asc
Description: OpenPGP digital signature