On Fri, Jan 28, 2011 at 5:53 PM, Stephan Beal <[email protected]> wrote:
> Sorry for all the noise tonight/this morning, but i'm on a hacking high...
>
> How's this for tickets info?
>
> stephan@ludo:~/cvs/fossil/fossil-sgb$ ./fossil tick list reports
> Available reports:
> report number    report title
> 0    full ticket export
> 1    All Tickets
> 2    All open tickets.
> 3    Open by type
> 4    Not Closed or Fixed, Doc or Feature
> stephan@ludo:~/cvs/fossil/fossil-sgb$ ./fossil ticket show -J --limit 2 1
> {
>     "columns":[
>         "bgcolor",
>         "#",
>         "mtime",
>         "type",
>         "status",
>         "subsystem",
>         "title"
>     ],
>     "rows":[
>         {
>             "bgcolor":"#cfe8bd",
>             "#":"8ae201d843",
>             "mtime":"2008-07-20 15:12:00",
>             "type":"Incident",
>             "status":"Fixed",
>             "subsystem":"one",
>             "title":"Bug tracker is not working"
>         },
>         {
>             "bgcolor":"#cfe8bd",
>             "#":"c7b35be884",
>             "mtime":"2008-07-23 13:03:24",
>             "type":"Incident",
>             "status":"Fixed",
>             "subsystem":"one",
>             "title":"Fossil fails to recognize its repository db as a known
> file."
>         }
>     ]
> }
> stephan@ludo:~/cvs/fossil/fossil-sgb$ ./fossil ticket show 1 "title LIKE
> '%tracker%'" -j
> {"columns":["bgcolor", "#", "mtime", "type", "status", "subsystem",
> "title"],
> "rows":[{"bgcolor":"#cfe8bd", "#":"8ae201d843", "mtime":"2008-07-20
> 15:12:00",
> "type":"Incident", "status":"Fixed", "subsystem":"one", "title":"Bug tracker
> is not working"}]}
>
> The content is basically the same (same fields) as 'ticket show', except
> that in json mode the -l/--limit parameter takes on the meaning of "limit"
> in the "LIMIT n" SQL sense of the word.
>
> Note that the underlying sql-to-json code is the same, regardless of the
> queries we're outputing, so the structure for all generated JSON will be the
> same. i.e. please no special requests in terms of structure, except maybe in
> really special cases.
>
> :-?

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.

-B
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to