[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Monotone-devel] Re: Future of monotone
From: |
Thomas Moschny |
Subject: |
Re: [Monotone-devel] Re: Future of monotone |
Date: |
Mon, 28 Jan 2008 19:54:01 +0100 |
User-agent: |
KMail/1.9.6 (enterprise 0.20071204.744707) |
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.
- Re: [Monotone-devel] Re: Future of monotone, (continued)
- Re: [Monotone-devel] Re: Future of monotone, Thomas Moschny, 2008/01/28
- [Monotone-devel] Re: Future of monotone, Bruce Stephens, 2008/01/28
- Re: [Monotone-devel] Re: Future of monotone, Thomas Moschny, 2008/01/28
- Re: [Monotone-devel] Re: Future of monotone, Markus Schiltknecht, 2008/01/28
- Re: [Monotone-devel] Re: Future of monotone, Thomas Moschny, 2008/01/28
- [Monotone-devel] Re: Future of monotone, Bruce Stephens, 2008/01/28
- Re: [Monotone-devel] Re: Future of monotone, Thomas Moschny, 2008/01/28
- Re: [Monotone-devel] Re: Future of monotone, Markus Schiltknecht, 2008/01/28
- Re: [Monotone-devel] Re: Future of monotone, Thomas Moschny, 2008/01/28
- Re: [Monotone-devel] Re: Future of monotone, Markus Schiltknecht, 2008/01/28
- Re: [Monotone-devel] Re: Future of monotone,
Thomas Moschny <=
- Re: [Monotone-devel] Re: Future of monotone, Markus Schiltknecht, 2008/01/28
- Re: [Monotone-devel] Re: Future of monotone, Thomas Moschny, 2008/01/28
- [Monotone-devel] Re: Re: Future of monotone, Pavel Cahyna, 2008/01/28
- Re: [Monotone-devel] Re: Future of monotone, Thomas Keller, 2008/01/28
- Re: [Monotone-devel] Re: Future of monotone, Derek Scherger, 2008/01/28
- Re: [Monotone-devel] Re: Future of monotone, Nathaniel Smith, 2008/01/28
- Re: [Monotone-devel] Re: Future of monotone, Thomas Moschny, 2008/01/29
- [Monotone-devel] Re: Future of monotone, Bruce Stephens, 2008/01/29
- Re: [Monotone-devel] Re: Future of monotone, Julio M. Merino Vidal, 2008/01/29
- [Monotone-devel] Re: Future of monotone, Bruce Stephens, 2008/01/29