On 30/08/2013 11:28, Robbert-Jan wrote:
> Hi,
>
> I like to propose a more consistent syntax for computed columns and
> identity columns:
>
> Computed columns are now defined in DDL as
>
> [] GENERATED ALWAYS AS ()
>
> while identity columns (as of FB 3.0 CORE-1385) are defined as:
>
>
> I also am not sure if a GENERATED BY DEFAULT AS ... makes sense for a
> computed column, as it would imply it is a normal column that has a default
> (which already has a separate clause) and not a computed one.
That also struck me as odd.
DEFAULT only makes sense for persisted fields, sinc
Thanks Adriano, Sean and Mark,
You are right. I do not no what I was thinking but specifying BY DEFAULT for
computed columns makes indeed no sense.
Kind regard,
Robert
On 30/08/2013 11:28, Robbert-Jan wrote:
> Hi,
>
> I like to propose a more consistent syntax for computed columns and
> identit
On Fri, 30 Aug 2013 16:28:37 +0200, "Robbert-Jan"
wrote:
> Hi,
>
> I like to propose a more consistent syntax for computed columns and
> identity columns:
>
> Computed columns are now defined in DDL as
>
> [] GENERATED ALWAYS AS ()
>
> while identity columns (as of FB 3.0 CORE-1385) are defin
Hi,
I like to propose a more consistent syntax for computed columns and identity
columns:
Computed columns are now defined in DDL as
[] GENERATED ALWAYS AS ()
while identity columns (as of FB 3.0 CORE-1385) are defined as:
{|} GENERATED {ALWAYS|BY DEFAULT} AS
IDENITITY
Note the difference
