Resolving Ambiguous Date References in Joined-Table Normalization

Summary

This troubleshooting note describes a SQL binder error that occurs when a normalization function is used in a query joining two stock-factor tables. Both tables contain a date column, so passing an unqualified date reference to the function leaves the database unable to determine which column is intended. The example query combines market-capitalization, dividend-yield, and KDJ-derived values into a weighted score alongside technical indicators.

The error message identifies the two possible date columns by their table aliases. The post’s title asserts that the normalization function applies only to a single table, but the document does not provide a fix or a confirmed workaround. It therefore helps identify a column-reference ambiguity, but does not establish whether normalization across joined data is unsupported or how the score should be computed. No strategy results or validation are reported.

Key ideas

• The example query joins fundamental and technical stock-factor tables that both contain a date field.
• An unqualified date argument to the normalization function triggers an ambiguity error.
• The error points to the date columns on the two joined table aliases as possible references.
• The post does not show a solution or validate the weighted factor score.

Tags

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