Re: [Monotone-devel] Re: Future of monotone

[Thomas Moschny]

Markus Schiltknecht wrote:
> Thomas Moschny wrote:
> > name = 'commit',      value = (author, date, comment=changelog, branch)
> > name = 'tag',         value = (author, date, comment, tag)
> > name = 'suspend',     value = (author, date, comment, branch)
> > name = 'test-result', value = (author, date, comment?, value)

[...]

> Well, that's pretty much what I meant. However, seen from the database
> layer, I certainly wouldn't stuff all that in a single 'value' field.

Maybe. I wrote it that way for brevity. As some certs may have more logical 
value fields then others, but should all be put in the same SQL table, you 
would have to stuff some valued into the same field (from the tables pov), 
no?

> A new revision_certs table could IMO look like:
>
> CREATE TABLE new_revision_certs
> (
>       hash not null unique,   -- consistency checking hash
>       rev_id not null,        -- joins with revisions.id
>       name not null,          -- name of the cert
>       date not null,          -- timestamp of the cert
>       author not null,
>       signer not null,
>       signature not null
> );

There's something missing. Where would you put the 'comment', 'branch', 'tag' 
and 'value' data from the table above? 

Regards,
Thomas

signature.asc
Description: This is a digitally signed message part.