Re: [Monotone-devel] Re: Is there something like libmonotone?

[Nathaniel Smith]

On Mon, Jan 31, 2005 at 09:31:54AM +0100, Christof Petig wrote:
> Additionally monotone (IIRC) caches cert signature evaluation (which is
> also costly IIRC).

It is costly, but actually we currently don't cache.

> So a command line automation interface would be much
> faster and 'echo cmd | monotone automate interact' is easy enough to
> omit a non interactive interface completely.

Mm, not so sure there; firstly because implementing the
read-eval-print loop in monotone is a chunk of new code, so it's less
incremental to develop, and secondly because we'd need to define some
sort of framing protocol on the output, so clients could tell where
the boundaries between different command outputs were, and this extra
framing junk would make the 'interact' interface much less useful to
shell scripts and the like.

> Wish list:
> - query heads
> - query ancestors

Ancestors of a given revision, or the whole graph?  (I guess both are
useful.)

> - query certs
> - search for a certain ID (by using selectors (if this was the correct
> name))
> - query manifest contents
> - query file contents

- query revision contents

> - query diffs
> - execute any sql command

No.  The whole point of this exercise is to define a stable,
supportable interface.  Exposing the database schema directly would
either mean that the interface isn't stable, or that we'd be
straightjacketed with respect to things like performance tweaking and
feature addition.

> - release the database and reaquire it (pause)

Hmm, interesting point.  Perhaps this would just happen automatically
between each command?

-- Nathaniel

-- 
"...All of this suggests that if we wished to find a modern-day model
for British and American speech of the late eighteenth century, we could
probably do no better than Yosemite Sam."