OBEROn - Bug Trace - Oberon Platform
Viewing Issue Advanced Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
65 OOQL language minor have not tried 2011-09-16 19:00 2011-09-16 19:05
Reporter: administrator Platform:  
Assigned To: administrator OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 2.4 - DB build 0062  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2.5 - DB build 0064  
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 ;
Steps To Reproduce:
Additional Information:
Relationships
Attached Files:
Issue History
Date Modified Username Field Change
2011-09-16 19:00 administrator New Issue
2011-09-16 19:01 administrator Fixed in Version => 2.5 build 00xx
2011-09-16 19:01 administrator Target Version => 2.5 build 00xx
2011-09-16 19:01 administrator Status new => resolved
2011-09-16 19:01 administrator Resolution open => fixed
2011-09-16 19:01 administrator Assigned To => administrator
2011-09-16 19:05 administrator Note Added: 0000099
2011-09-16 19:05 administrator Note Edited: 0000099
2011-09-16 20:20 administrator Note Edited: 0000099
2012-07-31 10:06 arkoberonplm Issue Monitored: arkoberonplm

Notes
(0000099)
administrator   
2011-09-16 19:05   
(edited on: 2011-09-16 20:20)
new OOQL commands:

object show <ID_List> view <View_Name> token ...;
link show <ID_List> view <View_Name> token ...;
object navigate <ID> view <View_Name> filter <Object_Conditions> getlink filter <Link_Conditions> token ...;
query immediate object <ClassPattern> <NamePattern> <RevPattern> view <View_Name> token ...;
query execute <QueryName> view <View_Name> token ...;

For the navigate command the properties of object (get) and link (getlink) are mixed respecting the order defined for the view columns.
When token is xml, the tags are the column names instead of the property names