Dear support:
Changelog says: Queries can now be defined using EXEC_SQL statement
This sounds great.
Just trying to get my head around this.
So instead of “find all customer” in the text tab of a query, it would be
EXEC_SQL ’select * from customer’ ? (I assume no)
Or do I need to explicitly specify field names? (I assume yes)
As in EXEC_SQL ’select name,city,state from customer’ ?
Does this allow tag replacements using << >> notation?
As in EXEC_SQL ’select name,city,state from customer WHERE ’ + <<LoggedInRegularUser.myWhere>>
(Or maybe there is no need if a field is used directly)
Can a field be used for the entire parameter?
As in EXEC_SQL LoggedInRegularUser.myQuery ?
Can you share your thoughts on why this was implemented?
There must be someone specific who had a need for this.
What business case does this solve?
Thx
Changelog says: Queries can now be defined using EXEC_SQL statement
This sounds great.
Just trying to get my head around this.
So instead of “find all customer” in the text tab of a query, it would be
EXEC_SQL ’select * from customer’ ? (I assume no)
Or do I need to explicitly specify field names? (I assume yes)
As in EXEC_SQL ’select name,city,state from customer’ ?
Does this allow tag replacements using << >> notation?
As in EXEC_SQL ’select name,city,state from customer WHERE ’ + <<LoggedInRegularUser.myWhere>>
(Or maybe there is no need if a field is used directly)
Can a field be used for the entire parameter?
As in EXEC_SQL LoggedInRegularUser.myQuery ?
Can you share your thoughts on why this was implemented?
There must be someone specific who had a need for this.
What business case does this solve?
Thx
Click Here to see a collection of my tips & hacks on this forum? Or search for "JaymerTip" in the search bar at the top.
Jaymer
Aware Programming & Consulting - Tampa FL
Jaymer
Aware Programming & Consulting - Tampa FL