Issue 16146

Summary: have per-document DB Context / Datasources
Product: Base Reporter: ldegener <afblukas>
Component: codeAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P4 CC: issues
Version: OOo 1.1 Beta2   
Target Milestone: ---   
Hardware: All   
OS: Linux, all   
Issue Type: ENHANCEMENT Latest Confirmation in: ---
Developer Difficulty: ---

Description ldegener 2003-06-27 12:19:55 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
Comment 1 marc.neumann 2003-06-27 12:38:07 UTC
assign to bh and set target
Comment 2 Frank Schönheit 2003-07-01 14:39:12 UTC
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 ...
Comment 3 bettina.haberer 2003-07-01 15:12:22 UTC
BH->MSC: Please don't set target milestones for Feature / Enhancements. 
Comment 4 Frank Schönheit 2003-07-01 15:50:38 UTC
valid exception, IMO. Untargeting.
Comment 5 Frank Schönheit 2003-07-01 16:00:48 UTC
valid object, IMO. Untargeting.
Comment 6 ldegener 2003-07-02 13:09:18 UTC
(->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. :-) 
Comment 7 Frank Schönheit 2003-07-02 14:13:14 UTC
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 ....
Comment 8 hans_werner67 2004-02-02 12:23:57 UTC
change subcomponent to 'none'
Comment 9 bettina.haberer 2010-05-21 14:46:09 UTC
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".