A few doubts about ticket fields and TracReports
Olemis Lang
I was implementing TracGViz version 1.3.3 (which is almost ready ;)
and the side-effect is that I have a few doubts. I'd appreciate if
someone either replies with the answer or with a link to the page(s)
where I could find further info about the subjects involved ;)
Here are some of them :
About ticket fields (This ones are in my «I dont know repository»
since version 1.3.2 ;) and TracReports :
- What are all ticket field types ? So far I know about `text`, `textarea`,
`radio`, and `select`. Is that all ?
- Is there a way to (declare | incorporate) further types to be used
with ticket
fields ? How ?
- AFAIK the values of (custom ) ticket fields returned by TicketRPC.get are
*ALWAYS* (Python) strings. Is that True ? Is possible that one of
these values
be an integer or an instance of some other class ?
- How to know what component(s) added a custom field ?
- How to get (programmatically ;) the results included in a report defined
using a query URL (i.e. report's SQL starts with `query:?` or `?`) ?
- Consider the case when I have executed a TracReport defined using plain SQL.
Let's say I have opened a cursor so as to retrieve the data (SQLite backend
;). At this point I wanna know the name and type of each column in the
result set so I use the cursor's `.description` attribute. In this case I
get back tuples like `('version', None, None, None, None, None, None)` which
say nothing about the type of values in any column. OTOH DB API 2.0 states
that «The first two items (name and type_code) are mandatory». So what's
happenning ?
Thnx in advance !
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
Olemis Lang
> Hello everybody !
>
> - How to get (programmatically ;) the results included in a report defined
> using a query URL (i.e. report's SQL starts with `query:?` or `?`) ?
> - Consider the case when I have executed a TracReport defined using plain SQL.
> Let's say I have opened a cursor so as to retrieve the data (SQLite backend
> ;). At this point I wanna know the name and type of each column in the
> result set so I use the cursor's `.description` attribute. In this case I
> get back tuples like `('version', None, None, None, None, None, None)` which
> say nothing about the type of values in any column. OTOH DB API 2.0 states
> that «The first two items (name and type_code) are mandatory». So what's
> happenning ?
>
BTW, I forgot to mention I need both of these for ReportRPC implementation.