[rt-users] Reports

[Todd Chapman]

On Fri, Nov 04, 2005 at 10:19:39AM -0600, Bob Goldstein wrote:
> 
>   I had a similar issue, and wound up using direct SQL.
>   I wanted to find all open tickets in a few selected queues,
>   where the requestor was the last to correspond, and in which
>   that correspondance was more than 2 days ago.  (E.g. we're
>   ignoring the client, so I need to rap some knuckles.)
> 
>   I thought, go to the query builder, have it tell me the
>   correct TicketSQL, then use that with the CLI in a cron job.
>   But I was just unable to figure out the TicketSQL for this.
> 
>   I would never update the db without using the perl API.
>   But it seems to me that using direct SQL for reports
>   is fairly benign, no?  Yes, the reports can fail if an
>   upgrade changes the schema in a backward non-compatible
>   way, or can become ineffecient if there are new
>   ways to do things.  But overall, this is a reasonable
>   risk, is it not?
> 
>      bobg

As long as you also want to risk having to redo your
reports if a future RT version has a schema change.