Yeah, we should. May need to split the UI for SQLSelect and SQLExec in the
Modeler into 2 separate queries.
> On Jul 18, 2022, at 4:37 PM, John Huss wrote:
>
> Sounds good. For #3 on SQLTemplate, will these still be able to be defined
> in the modeler? I like being able to do that, though I onl
Sounds good. For #3 on SQLTemplate, will these still be able to be defined
in the modeler? I like being able to do that, though I only use a single
database target for the SQL.
On Fri, Jul 15, 2022 at 2:40 PM Andrus Adamchik wrote:
> Another block of ideas for 5.0. Related to expressions and que
Another block of ideas for 5.0. Related to expressions and queries...
0. Terse and consistent Expression API. 90% of expressions are done with
Properties now, but the remaining 10% are clunky and inconsistent. I am
thinking the main class (interface) should be called "Exp", combining static
met
