The $sqlquery-export operation has a repeating view parameter (with name, viewReference and viewResource parts) for supplying the ViewDefinitions that a SQLQuery Library's relatedArtifact entries depend on. $sqlquery-run has no equivalent, so there is no way to satisfy a query's ViewDefinition dependencies inline when running synchronously.
Looking at the history, the view parameter appears to have been introduced when $sqlquery-export was added (48920a8, closing #319) rather than as a deliberate design decision - #319 only asked for an async mirror of $sqlquery-run plus the export-control parameters from $viewdefinition-export, and $sqlquery-run was never reconciled afterwards.
If anything, the asymmetry is backwards: the synchronous run operation is the natural home for the ad-hoc workflow (inline queryResource plus inline ViewDefinitions, nothing stored on the server), yet it is the one operation that cannot accept views.
Whichever shape the view parameter ends up taking (#384 questions the value of viewReference and the undefined binding semantics), the two operations should agree: either both accept ViewDefinition table sources or neither does.
The
$sqlquery-exportoperation has a repeatingviewparameter (withname,viewReferenceandviewResourceparts) for supplying the ViewDefinitions that a SQLQuery Library'srelatedArtifactentries depend on.$sqlquery-runhas no equivalent, so there is no way to satisfy a query's ViewDefinition dependencies inline when running synchronously.Looking at the history, the
viewparameter appears to have been introduced when$sqlquery-exportwas added (48920a8, closing #319) rather than as a deliberate design decision - #319 only asked for an async mirror of$sqlquery-runplus the export-control parameters from$viewdefinition-export, and$sqlquery-runwas never reconciled afterwards.If anything, the asymmetry is backwards: the synchronous run operation is the natural home for the ad-hoc workflow (inline
queryResourceplus inline ViewDefinitions, nothing stored on the server), yet it is the one operation that cannot accept views.Whichever shape the
viewparameter ends up taking (#384 questions the value ofviewReferenceand the undefined binding semantics), the two operations should agree: either both accept ViewDefinition table sources or neither does.