Skip to content

Conversation

@robertcoen
Copy link
Contributor

Allow dataaccess queries to be executed from kx dashboards and also maintain TorQ's .z.ps functionality for queries made from kx dashboards.

// Use upserting logic to determine behaviour
options::default,o;
if[`ordering in key o;options[`ordering]: go each options`ordering];
o::adjustqueries[o;partdict o];
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are o and options global variables? Can't the pre-processing funtion just return a result?

@@ -1,6 +1,5 @@
\c 200 2000
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

don't think we want this

}

//Define the current .z.ps as a new function to be called in dashps
.z.ops:@[.:;`.z.ps;{.:}];
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

don't use .z name space for custom functions
Also I think that should be value rather than .:

@jonnypress
Copy link
Contributor

@robertcoen can you squash and merge this if it's good to go?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants