Hi everybody, We're now doing some research on h2-1.4.192. During code reading of CRUD of a MVTable, I'm confused with the design and implementation of updateRows in Table.
As far as I know, current Implementation is to first remove the old rows and the add new ones. I'm wondering what's the target of this implementation. For example, whether it is possible for us to keep a column level undo log in TransactionStore and change corresponding columns in place at update time? Are there any serious problems going to happen under such modification? Thanks a lot! -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
