> always as " but couldn't find anything, except maybe by
Uriah Eisenstein <email@example.com
> I searched around for the actual implementation of column "generated
> digging into Derby source code which I don't want to... I want toHi Uriah,
> know whether a generated column is a "real" column existing within
> the DB storage, and is updated whenever the columns it depends on are
> updated - or is it a "virtual" column which is recalculated whenever
> it is read. I don't have a specific need for it right now, but such
> columns can be useful for indexing and such, e.g. of case-insensitive
> strings or of UDTs, so I think it is useful to know whether the price
> is mainly in space requirements (if they're "real") or just in
> performance when reading.
The generated columns are physical columns stored in the tables, and
they are updated whenever a column they reference changes. You can also
create indexes on the generated columns.