Tim Diggins wrote: > quick questions (more waffle for each question below): > > 1) is there any way of customizing what you get when you click "View > Tickets" with reports disabled? >
Yes, this was discussed on trac-dev, and the current idea is to have a [ticket] default_report configuration setting, which you can set to anything ... even a Wiki page as you suggested (see http://groups.google.com/group/trac-dev/msg/514ed4f34255d722 for details). This is not yet done, but should be soon. > 2) http://trac.edgewall.org/wiki/TracReports has suggested that the > "report" module is being phased out, but is this still true > What is problematic with the reports is that using them implies an intimate knowledge of the Trac database model and often of the SQL dialect of the database used (especially for date/time related queries). This means that reports can eventually break at each Trac upgrade or database migration (less frequent, but still...). This being said, those arguments only stand as long as the report queries are written in SQL. As you noticed, with #1735 Trac custom queries can be saved as reports as well, so those inconveniences are not relevant anymore. I think that rather than being phased out, the report module will evolve and move away from supporting direct SQL queries and rather focus on the TracQuery language, which itself should evolve a lot in order to match the possibilities currently offered by SQL queries. See also http://trac.edgewall.org/ticket/2465. -- Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
