opt: virtual columns in the primary key should be consider STORED #75874
Labels
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
T-sql-queries
SQL Queries Team
From the perspective of the optimizer, any virtual column in the primary key should be considered STORED because it acts exactly like a stored computed column in a primary key: it can be produced from a primary index scan and any secondary index scan without needing to be calculated.
Related: #75147
The text was updated successfully, but these errors were encountered: