Computed columns and Database Builder

[Paolo F Cantoni]

One of our end-users has the following table definition:

Code: [Select]

CREATE TABLE [dbo].[Test](
       [Quantity] [float] NULL,
       [Price] [money] NULL,
       [Name] [nchar](10) NULL,
       [Revenue]  AS ([Quantity]*[Price])
) ON [PRIMARY]
GO
As can be seen it contains a computed column (Revenue).  He tried to reverse engineer it with DBB and any mention of computability disappeared.  Forward engineering then showed it was just a sim0ple float field.

Can such columns be reversed or forward engineered?  What is the appropriate syntax?  Is a Feature Request required?

TIA,
Paolo

[Richard Freggi]

I'm curious, as far as I can think, that's not DDL.  So, no.

[Paolo F Cantoni]

I'm curious, as far as I can think, that's not DDL.  So, no.

It's part of SQL server DDL:
"A computed column is a virtual column that is not physically stored in the table unless the column is marked PERSISTED. A computed column expression can use data from other columns to calculate a value for the column to which it belongs. You can specify an expression for a computed column in SQL Server 2019"

However, the question has been asked before in the forum - as far back as 2005.  I was just hoping that with the new DBB functionality, the issue might have finally been resolved.

It would seem not.

Paolo