Using SQL Factor Formulas as Expression Features

Summary

This brief BigQuant platform note explains how to use a factor written as a SQL function and field within a strategy workflow. It distinguishes platform expression factors, described as an operator paired with a field, from SQL factors, described as a function paired with a field. The practical answer is that a SQL factor formula can be entered in the input feature list’s expression-feature module, with a formatting restriction: do not append commas after individual features.

The exchange also asks whether an example factor could be placed in a linear strategy template and shared for backtesting, but it does not provide that template, a worked factor, or test results. As a result, this is a narrow platform usage tip rather than guidance on factor construction or investment merit. Users would still need to verify that their SQL expression, fields, and feature syntax are supported in their particular workflow.

Key ideas

• A SQL factor can be entered in the platform’s expression-feature input module.
• The note distinguishes expression factors from SQL factors by their operator or function and field components.
• Feature entries should not end with commas.
• The document does not include a worked factor, strategy template, or backtest evidence.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.