Sign up
Log in
My Platform
Tools
Tools
Go back
Downloads
IPP
Licensing
Learn
Learn
Go back
Training
Welcome
Guided Paths
Training Planner
Courses
Tech Talks
Classroom
Certifications
Documentation
Overview
OutSystems 11
Best Practices
How-to Guides
Community
Community
Go back
Home
Jobs
Forums
Forge
Ideas
Members
Badges
Support
OutSystems.com
Sign up
Log in
Community
›
Ideas
›
Simple Query: Control output entities\structures
Advanced Search
0
Followers
11
Likes
Simple Query: Control output entities\structures
Carlos Henriques
Carlos Henriques
Manager
at
Becker Professional Education
+ 5
#90
in Community Rank
Aggregates & Queries
Implemented
on 24 Sep 2014
OutSystems 9
In my opinion Simple Query lacks the opion to choose if each entity/structure is part of the ouput or not. Something like the Advance Query.
It could be a simple flag property on each entity, where we would say if that entity will or not be part of the ouput or if it just used to join the tables.
Sometimes we need to make a query, joining multiple tables, but we just want to output one of the entities. This would save the need to create custom structures or "mixed" record lists.
Created on 31 Oct 2012
Comments (2
)
Kilian Hekhuis
5 Nov 2012
Kilian Hekhuis
MVP
Functional Specialist
at
MAIN Energie
+ 12
#2
in Community Rank
Agreed. It won't often be a problem, but on occasion I've found myself writing an Advanced Query for just this reason.
Fernando Sousa
5 Nov 2012
Fernando Sousa
at
WeDo Technologies
+ 1
#1 492
in Community Rank
Supposedly, the optimizer will output only the entities and attributes used in your flow.
Remaining attributes will be selected as NULL to fill the entity/structure (e.g. SELECT {USER}.[Id], NULL, NULL, NULL, ... FROM {USER} ...)
Nevertheless, it would be better not to have those dummy attributes selected at all...
views
943
Followers
0
Loading...
Loading
(hidden) New Badge Popup