Apache OpenOffice (AOO) Bugzilla – Issue 16146
have per-document DB Context / Datasources
Last modified: 2013-02-07 22:33:07 UTC
It would greatly simplify my current work with OOo, if i could design (parameterized) queries for a specific document/template. (or maybe have a per document DB context). Those queries should also be shown/editable by the DataSourceBrowser
assign to bh and set target
LDegener, if you describe in more detail what you do, then it's more probable that whatever will be implemented (if it will) meets your need. In the current form, the basic idea is clear, but you encourage us guessing what exactly you want ...
BH->MSC: Please don't set target milestones for Feature / Enhancements.
valid exception, IMO. Untargeting.
valid object, IMO. Untargeting.
(->Frank) Again, Sorry for beeing vague. This issue is related to the same problem as issue 16145: I need to associate a subset of the records returned by one or more queries to a certain document. If the parameterization as described in 16145 is not possible, one way around this problem would be to create specialized queries for each document in question. But then all those queries would show up in the DataSourceBrowser, without any possibility for the user to tell which of them are related to the document he is currently working on. The solution that i would like to suggest is to add the possibility of defining queries not in a "global" context, like it is currently the case, but rather in the context of the current document. Then, the Datasource browser would, in addition to the globaly defined datasources and queries, show a node for each loaded document (in the treeview on the left, i think it is called "explorer"?) which in turn would contain datasources and queries defined in the context of this document as child nodes. Sorry for potentialy weird vocabulary or spelling, i'm not a native speaker. :-)
thanks for the explanation - this made it clearer to me (your englis is perfect :). The idea to have documents in the explorer, and thereunder the data sources local to this document, sounds interesting ....
change subcomponent to 'none'
To grep the issues easier via "requirements" I put the issues currently lying on my owner to the owner "requirements".