On Sat, Jan 29, 2011 at 2:59 AM, Brian Smith <[email protected]> wrote:
> I'd like it if "uuid" could be standardized on. It took me a couple
> looks to notice that "#" was uuid.
> I realize this likely just means changing the SQL in this particular
> case, but, I should be able to get the "uuid" key out of every single
> object returned by these JSON functions.
>
We're just pushing whatever the ticket SQL is generating, which looks
something like:
SELECT
CASE WHEN status IN ('Open','Verified') THEN '#f2dcdc'
WHEN status='Review' THEN '#e8e8e8'
WHEN status='Fixed' THEN '#cfe8bd'
WHEN status='Tested' THEN '#bde5d6'
WHEN status='Deferred' THEN '#cacae5'
ELSE '#c8c8c8' END AS 'bgcolor',
substr(tkt_uuid,1,10) AS '#',
datetime(tkt_mtime) AS 'mtime',
type,
status,
subsystem,
title
FROM ticket
WHERE status IN ('Open', 'Verified')
ORDER BY type, mtime DESC LIMIT 1
i'm not touching the "core queries", except to add an "AS" clause on some of
them where doing so does not break the query and avoids JSON keys which look
like "SELECT ... FROM..." (from subselects).
As far as i understand, certain other automation depends on some of those
conventions, like the '#' lable.
We can of course create new queries for tickets for this purposes, and are
not necessarily bound to what the "ticket" command currently generates. i'm
just looking for places to try it out at the moment.
--
----- stephan beal
http://wanderinghorse.net/home/stephan/
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
