On 22/07/12 12:25, Stephan Beal wrote: [...] > Another good idea. How about this minor simplification: > > fossil custom foo # uses current branch > fossil custom /branch/foo # use branch/ckout version > > i.e. if it starts with a / we'll assume the first path prefix is a > symbolic name.
That does introduce an ambiguity with absolute paths, but yeah.
[...]
> That's my only concern about it as well (but it's minor). Maybe we can
> find a more compact syntax.
You can solve any problem with an extra level of indirection!
Make:
fossil custom blah ...
...equivalent to:
fossil custom -f /tip/.auto.th1 -- blah ...
That way the user can configure things however they like.
[...]
> Funnily enough... the query API restricts users to SELECT-like queries
> (those with result _columns_), but i _really_ want a particular
> temporary view in one of my scripts. However, i don't know how to allow
> that type of thing without opening up the possibility for a user losing
> data via script code, so i have refrained.
I wonder if there's some magic that could be done with ATTACH DATABASE?
For example, creating a temporary (or persistent, if the script wanted
it) database, attach the main database to it in read only mode, which
would give something the script could do arbitrary SQL on while still
being reasonable safe...
--
┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ─────
│
│ life←{ ↑1 ⍵∨.^3 4=+/,¯1 0 1∘.⊖¯1 0 1∘.⌽⊂⍵ }
│ --- Conway's Game Of Life, in one line of APL
signature.asc
Description: OpenPGP digital signature
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
