Hi, Wondering if this rings a bell with anyone. I have some tables with a few million rows each. It's all speedy enough unless I have a computed column (for example VARCHAR(5) AS (SELECT ... FROM indexed_relation...). To begin with, if I add an extra million rows to a table that has no computed column, the operation only takes a few seconds. If I then add a computed column to that table, for example a computed column that selects on a related table (using PK), the 'alter table' takes a few seconds. So there is no problem with the computed select column per se. But then, if I insert another million rows, the operation takes hours (if it ever finishes at all...). So inserting rows when there is an existing computed select column is unusably problematic. Just thought someone else might have definitely or definitely NOT experienced this same issue. It's consistent for H2 1.2 as well as 1.3. (I'll try to file a test case and bug report in the next few days, but have to get other things done to meet a deadline, having lost a whole afternoon and most of today to tracing this issue.)
James -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-/tS1mfNz04fEJ. 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.
