(v24) Supported SQL-Like Expressions

Supported SQL-Like Expressions

This applies to: Visual Data Discovery

Symphony's custom metrics support the following SQL-like expressions:

Expression	Description
WHERE	Use WHERE to filter by a condition. Data will only be included in the custom metric if the condition that follows is true. For example: COUNT(weatherdelay) WHERE airportcode IN ('LAX', 'ORD', 'IAD') Row-level functions and expressions can be used in WHERE clauses in custom metrics. In a custom metric, WHERE clauses allow you to specify a formula without first creating a derived field. The WHERE clause must be in the leftmost part of the custom metric expression, but it can be expressed with a row-level function or any of the aggregate functions available for custom metrics. In the following example, the total planned sales is calculated for men. SUM(plannedsales) WHERE UPPER(gender) = 'MALE'
AND	Use AND to form a conjunctive condition. Data is only included in the custom metric if it meets both of the conditions connected by AND. The following example calculates the sum of deicing only if the broadphaseofflight includes LANDING and the airportcode is YYZ. SUM(deicing) WHERE broadphaseofflight IN 'LANDING' AND airportcode='YYZ'
OR	Use OR to for a disjunctive condition. Data is included in the custom metric if it meets either of the conditions connected by OR.  The following example calculates the sum of deicing if the broadphaseofflight includes LANDING or the airportcode is YYZ. SUM(deicing) WHERE broadphaseofflight IN 'LANDING' OR airportcode='YYZ'
BETWEEN...AND	Use BETWEEN to filter using a range of values. The following example counts the number of distinct records for weatherdelay that have cancelledflight counts between 2 and 10. COUNTD(weatherdelay) WHERE cancelledflight BETWEEN 2 AND 10
IN	Use IN to filter using a set of values. Data is included in the custom metric only if a data field matches one of the listed values. The following example calculates the sum of weatherdelay only for records in which the airportcode field is LAX, ORD, or IAD. SUM(weatherdelay) WHERE airportcode IN ('LAX','ORD','IAD')
NOT IN	Use NOT IN to filter using a set of values. Data is included in the aggregation only if a data field does not match one of the listed values. The following example calculates the sum of weatherdelay only for records in which the airportcode field is not LAX, ORD, or IAD. SUM(weatherdelay) WHERE airportcode NOT IN ('LAX','ORD','IAD')
TRANSFORM	Use TRANSFORM to filter based on a derived date. To derive a date with TRANSFORM, you must already have a time attribute configured in your data source. The following example calculates the sum of weatherdelay only for records in which the eventdate is for the previous period. In other words, if the visual is examining two weeks of data for weatherdelay, this calculation will provide data about the two weeks prior to that. SUM(weatherdelay) TRANSFORM eventdate=PreviousPeriod() To work correctly, data must be available for the periods of time considered.