Noel- Got it, thanks. We use H2 for those same reasons, Also, the ability to automate our integration tests using the same database engine as we use in production is awesome and reduces our operational support footprint.
FWIW- our contributed enhancements to the TCP client handling stem from wanting to improve automate management and monitoring tasks. Thanks, -Matt On Monday, September 9, 2019 at 12:56:47 PM UTC-5, Noel Grandin wrote: > > > > On Mon, 9 Sep 2019 at 17:45, Matt Pavlovich <ma...@hyte.io <javascript:>> > wrote: > >> >> Would you kindly elaborate on your last statement there about H2 is not >> intended to be used over a complex client network? >> >> > H2 is intended (mostly) to be small, reasonably fast, and reasonably > effective, without being overly complicated. > > Database Servers, in general, are intended to be deployed in locked down > and controlled environments. > > Normally, that means behind some kind of application server / web server / > etc. > > Now, of course, H2 __can__ be used in other environments, but then, you > are going to continue finding things just don't quite work right, > because now you are operating outside the intended design space. > > -- 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 h2-database+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/2cf1215a-c859-4ec2-9882-6a273a354a85%40googlegroups.com.
