| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
Hello,
Assuming I find a clean way of implementing scoping and filtering, one
of the questions I face is :
If In_Entity contains something like GLOBAL_ENTITY xyz <Sub_entity
Class wildcarding>, i.e. a 2-level AES specification and my scoping
parameter indicates that I want the entire containement tree, can I
*legally* return in my out_entity an AES specification containing more
than 2 <Class Instance> pairs ?
By *legally*, I mean will PM's etc accept it ?
Best wishes for 1992,
Philippe.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2005.1 | use of out_e | TOOK::CALLANDER | MCC = My Constant Companion | Mon Jan 06 1992 16:03 | 15 |
It is my understanding/interpretation that the SRM only says tha tyou must return the fully qualified primary identifier for the entity. If this means that the in entity oand out don't match, thenso be it. Now as to the catch, will this work with the PMs. As per my earlier mail to you, the only area of concern that jumps to mind is in the areas of wilcard support. I know the FCL makes use of out_e when expanding wildcards, or in completing multi part operations like attribute group support. I would suggest yo make sure you test each of these areas along with WITH clause support if you are going to attempt to do this. I would be interested in your results. thanks jill | |||||