Ah, I see. Well, we can handle large in-memory tables via our experimental "nio:" storage layer, but not streaming replication.
So you're obviously building something kind of streaming storage product on top of H2. Which is fine, I don't have a problem with that, but I still agree with Thomas - we're not intending to expose our SQL parsing infrastructure as an API, so we're not really interested in making your particular use-case easier. Sorry about that, wish you the best with your product. On the other hand, if you were going to contribute such a storage engine back to the core H2 community, then we'd be interested in integrating your patches. -- 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.
