We'll be able to do things like


COALESCE(IF(_fkSandT_Turnover='?',NULL,(SELECT _Turnover FROM SandT WHERE _Band = _fkSandT_Turnover)),
IF(_fkSandT_Staffing='?',NULL,(SELECT 'Staff: '+_Staff FROM SandT WHERE _Band = _fkSandT_Staffing)))

in computed columns?

Roy Lambert

Roy,

<< We'll be able to do things like
.....
in computed columns? >>

Never - computed columns are handled client-side, and therefore are unable
to resolve anything outside of the scope of the current table's columns.
Therefore, things like sub-queries and UDFs are out.

Is there any reason why you can't use a generated column instead ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


>Never - computed columns are handled client-side, and therefore are unable
>to resolve anything outside of the scope of the current table's columns.
>Therefore, things like sub-queries and UDFs are out.

Now you say that I remember. My personalised storage system is obviously due for replacement.

>Is there any reason why you can't use a generated column instead ?

Only my hatred of wasting space.

Roy Lambert

Roy,

<< Only my hatred of wasting space. >>

Just remember that the only space being wasted is disk space - computed
columns still use the same amount of memory as generated columns, and incur
additional CPU overhead.

--
Tim Young
Elevate Software
www.elevatesoft.com