Perhaps slightly off topic, but related to your comment about not having the queries in SQL:
I have a trac site that started life with SQL search queries. As I add new queries, they are in a more TracQuery language. But the old original queries stay as SQL. I would like to have all the queries in the non-SQL syntax. What is the easiest way to do this? Editing the search seems not to do this. Do I have to delete the query and then add it again new? My queries are all a mess. I really need to do a bit of housekeeping. Maybe I could dump all the defined queries somehow, edit this, and then re-import the queries? On Wed, Dec 2, 2015 at 6:14 AM, RjOllos <[email protected]> wrote: > > > On Friday, November 20, 2015 at 2:39:18 AM UTC-8, Mo wrote: >> >> Am Freitag, 26. Juni 2015 06:00:28 UTC+2 schrieb RjOllos: >>> >>> >>>> is it possible to share custom queries or reports with users, user >>>> groups or globally? From the users perspective that would mean to have an >>>> overlay of inherited queries and user-owned custom queries. >>> >>> >>> From what I can see the saved custom queries are available to all users. >>> You could restrict access to certain reports (saved queries) using >>> TracFineGrainedPermissions (1). See comments about that (2). >>> >>> (1) http://trac.edgewall.org/wiki/TracFineGrainedPermissions >>> (2) https://trac-hacks.org/ticket/11049 >> >> >> Hi, taking this topic up again... are there plans to rework the whole >> custom query section? Currently it is not very flexible, if I don't miss >> some things: > > > No plans that I know of. You may find it discussed in some tickets, but they > aren't currently scheduled. > >> >> What is the difference between custom queries and reports? AFAIK queries >> can be created with the gui while reports are plain SQL? But sometimes >> editing a custom query I end up with SQL as well. And the "View tickets" >> view shows reports and queries without notes which entry is a query or a >> report. > > > Custom queries have a special syntax that is portable across database > backends. The main downside to reports containing SQL is that it is > difficult to make them portable across SQLite, PostgreSQL and MySQL. > > Saving a custom query will put query syntax in the report SQL box, which you > might be confusing with having SQL. > > The other advantage to custom queries is that a saved custom query can be > further refined by the user. Custom queries are preferred. It is recommended > to only use reports if you can't accomplish your aims with custom queries. > >> >> Is it possible to clone a query/report? I tried creating a new report and >> copy the SQL from another report, but even then I need to adapt report= >> which feels very lowlevel. > > > On the page for any report/custom-query you should find a //Copy Report// > button. It should be present for any users with REPORT_CREATE. > >> >> According to the initial question there is no difference between user >> specific custom queries and shared queries. Currently all queries that are >> created by report admins are visible to all. >> Most users coming from Bugzilla like to have their own queries for their >> own projects. Then creating all available queries for all projects globally >> will increase the list a lot. Then having fixed ids in the report list will >> lead to wholes after removing reports. > > > I agree it is a valuable feature, however we are really lacking contributors > these days and the few of us that are working on the projects can't > implement every nice-to-have feature in the limited time we have available. > I'd like to get more people involved in the project, but that is difficult > even someone commits to working some patches. Hopefully things will pickup > in the coming year. > > http://trac.edgewall.org/ticket/9617 > > - Ryan > > -- > You received this message because you are subscribed to the Google Groups > "Trac Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/trac-users. > For more options, visit https://groups.google.com/d/optout. -- Roger Oberholtzer -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
