[Trac] Re: TicketQuery macro and Intertrac prefixes
Stephen Moretti wrote: Is it possible to use TicketQuery across trac environments using Intertrac prefixes? I guess I can do [othertrac:query:somequerystring link to query], but I'd like to have the query appear in the wiki page as per the TicketQuery macro. I guess that will never be possible for cross-environment queries, but that syntax will work in a multiple projects per environment setup (which is of course at this point not yet implemented). -- Christian --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com 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 -~--~~~~--~~--~--~---
[Trac] Re: TicketQuery macro and Intertrac prefixes
2008/11/19 Christian Boos [EMAIL PROTECTED] Stephen Moretti wrote: Is it possible to use TicketQuery across trac environments using Intertrac prefixes? I guess I can do [othertrac:query:somequerystring link to query], but I'd like to have the query appear in the wiki page as per the TicketQuery macro. I guess that will never be possible for cross-environment queries, but that syntax will work in a multiple projects per environment setup (which is of course at this point not yet implemented). Hmm I guess I'd need to really be using a common database (multiple schemas) for all the environments and make a macro that basically replicates ticketquery but can interrogate multiple schema, a la http://trac.edgewall.org/wiki/TracMultipleProjects/MultipleEnvironmentsSingleDatabase On a tangent Whats the issue with MySQL support? Is it down to the MySQL/Python Connector? Is that correct? Stephen --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com 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 -~--~~~~--~~--~--~---
[Trac] Re: TicketQuery macro and Intertrac prefixes
On Nov 19, 10:45 am, Stephen Moretti [EMAIL PROTECTED] wrote: 2008/11/19 Christian Boos [EMAIL PROTECTED] Stephen Moretti wrote: Is it possible to use TicketQuery across trac environments using Intertrac prefixes? I guess I can do [othertrac:query:somequerystring link to query], but I'd like to have the query appear in the wiki page as per the TicketQuery macro. I guess that will never be possible for cross-environment queries, but that syntax will work in a multiple projects per environment setup (which is of course at this point not yet implemented). Hmm I guess I'd need to really be using a common database (multiple schemas) for all the environments and make a macro that basically replicates ticketquery but can interrogate multiple schema, a lahttp://trac.edgewall.org/wiki/TracMultipleProjects/MultipleEnvironmen... On a tangent Whats the issue with MySQL support? Is it down to the MySQL/Python Connector? Is that correct? Stephen I don't see why you would need a 1 db/multiple project schema. The TracHours plugin has a multi-project query which I beleive works in the standard mutli-project setup. It does modify the database for it's purpose, but I think it could done. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com 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 -~--~~~~--~~--~--~---
[Trac] Re: TicketQuery macro and Intertrac prefixes
On Wed, Nov 19, 2008 at 09:17:00AM -0800, [EMAIL PROTECTED] wrote: On Nov 19, 10:45 am, Stephen Moretti [EMAIL PROTECTED] wrote: 2008/11/19 Christian Boos [EMAIL PROTECTED] Stephen Moretti wrote: Is it possible to use TicketQuery across trac environments using Intertrac prefixes? I guess I can do [othertrac:query:somequerystring link to query], but I'd like to have the query appear in the wiki page as per the TicketQuery macro. I guess that will never be possible for cross-environment queries, but that syntax will work in a multiple projects per environment setup (which is of course at this point not yet implemented). Hmm I guess I'd need to really be using a common database (multiple schemas) for all the environments and make a macro that basically replicates ticketquery but can interrogate multiple schema, a lahttp://trac.edgewall.org/wiki/TracMultipleProjects/MultipleEnvironmen... On a tangent Whats the issue with MySQL support? Is it down to the MySQL/Python Connector? Is that correct? Stephen I don't see why you would need a 1 db/multiple project schema. The TracHours plugin has a multi-project query which I beleive works in the standard mutli-project setup. It does modify the database for it's purpose, but I think it could done. To be fair, the TracHours multi-project query is fairly ad-hoc; it also does HTTP requests to get the RSS instead of reading from the DB which is less than ideal. I don't apologize for either of these things, mainly because no framework exists (to my knowledge?) to do this sort of thing in trac in a standardized way. I highly desire such a standardization of dialect whereby trac instances can talk to each other and plugins can talk to each other. But I'm realistic in that not only is this difficult to design, I think any solution (or even the idea of a solution) would be very contraversial. So roll your own? Jeff --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com 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 -~--~~~~--~~--~--~---
[Trac] Re: TicketQuery macro and Intertrac prefixes
On Wed, Nov 19, 2008 at 12:22 PM, Jeff Hammel [EMAIL PROTECTED] wrote: On Wed, Nov 19, 2008 at 09:17:00AM -0800, [EMAIL PROTECTED] wrote: I don't see why you would need a 1 db/multiple project schema. The TracHours plugin has a multi-project query which I beleive works in the standard mutli-project setup. It does modify the database for it's purpose, but I think it could done. To be fair, the TracHours multi-project query is fairly ad-hoc; it also does HTTP requests to get the RSS instead of reading from the DB which is less than ideal. I don't apologize for either of these things, mainly because no framework exists (to my knowledge?) to do this sort of thing in trac in a standardized way. I highly desire such a standardization of dialect whereby trac instances can talk to each other and plugins can talk to each other. But I'm realistic in that not only is this difficult to design, I think any solution (or even the idea of a solution) would be very contraversial. So roll your own? Jeff Assuming that each environment is located under a single parent directory, why not just go through each environment in the parent directory and open_environment() on it? I have lots of scripts and a few plugins that gather data from all environments on the server in this way. Query each environment's DB separately, and then combine the data in an intelligent way--that part depends entirely on what you're querying and what you intend to do with the data. Of course, that assumes all the environments are on the same server. If not, that's what the XML-RPC plugin is good for, though it certainly doesn't give you the same flexibility. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com 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 -~--~~~~--~~--~--~---
