Yeah, at the moment the way LINKED TABLE is implemented, we do transaction logging and undo on the H2 side of the connection, which as you've found is quite memory expensive.
What we really need is a LINKED TABLE that doesn't do that, that creates a new remote connection for each H2 connection and lets the remote DB do the transaction stuff.
If you feel like hacking, the relevant class is org.h2.table.TableLink On 2013-08-06 10:46, Heinz Mayer wrote:
If I insert large tables from H2 to Oracle, I get a out of memory exception
-- 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 http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
