| 
    ![]() ![]() ![]() ![]()  | 
    
| Anonymous | Login | Signup for a new account | 2025-11-04 04:14 CET | 
| Main | My View | View Issues | Change Log | Roadmap | Docs | 
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||
| 0000065 | [Oberon Platform] OOQL language | minor | have not tried | 2011-09-16 19:00 | 2011-09-16 19:05 | ||
| Reporter | administrator | View Status | public | ||||
| Assigned To | administrator | ||||||
| Priority | normal | Resolution | fixed | ||||
| Status | resolved | Product Version | 2.4 - DB build 0062 | ||||
| Summary | 0000065: Use the view definition to extract the object/link properties | ||||||
| Description | 
		Object "show"/"navigate" OOQL commands, link "show" and query "execute" commands allow to declare the list of properties to retrieve for each element.   Why not use directly a view for these commands instead of the "get" option? For example write: object navigate #00001-D25EA19A view <View_Name> token xml ; instead of object navigate #00001-D25EA19A get {name currentstage.admin.{name id}} getlink { id linktype active } token xml ; OR write: object show #00001-D25EA19A,#00001-D25EA19A view <View_Name> token xml ; as alternative of: object show #00001-D25EA19A,#00001-D25EA19A get {name currentstage } token xml ;  | 
||||||
| Additional Information | |||||||
| Tags | No tags attached. | ||||||
| Attached Files | |||||||
| 
 | 
|||||||
![]()  | 
     
       © 2008-2013 Mirko Solazzi | Website 
        Templates by IceTemplates.com 
    Please Read: Privacy Policy and Terms of Use  |