I think it would be a good idea if GENERATED/COMPUTED columns were passed through to table/query components as read only. Or better still a read only attribute that we could set on a column by column basis.

If there's one there already I would like to announce that I'm suffering from code blindness currently so pointing out the obvious would be welcomed.


Roy Lambert

Roy,

<< I think it would be a good idea if GENERATED/COMPUTED columns were passed
through to table/query components as read only. Or better still a read only
attribute that we could set on a column by column basis. >>

AFAIK, they are (flagged as read-only *and* passed through that way).  I
can't test it this very moment, but the source code says that it is
definitely doing so.

Tim Young
Elevate Software
www.elevatesoft.com

Tim


"_CallID" INTEGER GENERATED BY DEFAULT AS IDENTITY (START WITH 0, INCREMENT BY 1) NOT NULL,

comes through to a TEDBTable in D2006 as TAutoIncField (what I'd expect) but with ReadOnly in the persistent field set to False.

I didn't check COMPUTED properly. I picked the wrong column from a table and my memory was duff (surprise surprise). This time I checked the catalog and yes that does come through with ReadOnly set as True.

Looking at the GENERATED columns they are all of the above type so it could be specific to that.

Roy Lambert

Tim


Got it - its me being thick as usual - GENERATED BY DEFAULT vs GENERATED ALWAYS

Roy Lambert