> 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, since the default would be assigned instead of NULL if the column was not referenced in the INSERT statement. Computed fields are always calculated/resolved at runtime, so I can't see how a default could apply to computed. Sean ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
