Not at present.
We'd need a new feature that basically said "don't store/cache this
computed column"
If you want to work on such a thing, the place to start looking in the
code is probably by working backwards from this method:
org.h2.table.Column#computeValue(Session, Row)
You're also welcome to try running a profiler, and seeing if you can
spot something. It's quite possible your use case is triggering a
performance issue we haven't seen before.
On 2012-04-13 09:43, JND wrote:
In my case, as mentioned in my post, the table already contains
millions of rows. So when I add the computed column to the existing
table with those rows, you are saying the new calculated values are
NOT calculated for the existing rows during ADD COLUMN. So calculation
is deferred? Since the ADD COLUMN is fast, and the calculated values
are reliably present upon SELECT, the implementation is ideal. Is it
possible to get this behaviour with INSERT?
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
