RunQuery
Value members
Concrete methods
Summon all needed components and run executeQuery method
(Experiment with catching StaticTranslationMacro.apply
errors since they usually happen
because some upstream construct has done a reportError so we do not want to do another one.
I.e. if we do another returnError here it will override that one which is not needed.
if this seems to work well, make the same change to other apply___ methods here.
)
Summon all needed components and run executeQuery method
(Experiment with catching StaticTranslationMacro.apply
errors since they usually happen
because some upstream construct has done a reportError so we do not want to do another one.
I.e. if we do another returnError here it will override that one which is not needed.
if this seems to work well, make the same change to other apply___ methods here.
)
Expand dynamic-queries i.e. queries whose query-string cannot be computed at compile-time. Note that for now, QuotationType is only needed for dynamic queries (which is only needed to know whether you need to use ElaborateStructure or not. This is decided in the StaticTranslationMacro for static queries using a different method. I.e. since StaticTranslationMacro knows the AST node it infers Action/Query from that).
Expand dynamic-queries i.e. queries whose query-string cannot be computed at compile-time. Note that for now, QuotationType is only needed for dynamic queries (which is only needed to know whether you need to use ElaborateStructure or not. This is decided in the StaticTranslationMacro for static queries using a different method. I.e. since StaticTranslationMacro knows the AST node it infers Action/Query from that).
Execute static query via ctx.executeQuery method given we have the ability to do so i.e. have a staticState
Execute static query via ctx.executeQuery method given we have the ability to do so i.e. have a staticState