would allow nesting, e.g. +by name+descending+limit200
My guess is that we need to be able to push certain things from inner queries to outer ones. So, within SQL we have sort, dir, limit, offset. found_by is likely the most common source of this kind of weirdness, but we probably want a solution that does this regardless.
My guess is that the best idea is to use the outermost version of each of these that we have.
Outside of SQL we have append and view. Separate issues, I suppose.
When done, replace Tickets by tag by create with Ticket tags+by create+tix, same with Tickets by tag by name and Tickets by tag by update.
preserve arrangements in found_by+discussed in support tickets
preserve arrangements in found_by+relevant user stories