Hi, I agree. H2 is "good enough" for many use cases (and for some use cases it's even better than other databases), but it just can't compete with PostgreSQL when you need certain features. It's nice if switching to PostgreSQL is relatively painless.
Regards, Thomas On Wednesday, September 17, 2014, cowwoc <[email protected]> wrote: > On 17/09/2014 2:08 PM, Noel Grandin wrote: > >> Just for completeness - what does your H2 URL look like? >> > > jdbc:h2:c:/foo/bar/../database/target/database;MV_ > STORE=false;TRACE_LEVEL_FILE=4;LOCK_MODE=1 > > To be honest, if you are feeling the need to scale up, then PostgreSQL >> is a good solution. >> H2 is more focussed on ease of deployment and integration with Java, >> so I doubt that we're ever going to play in the same performance and >> scalability leagues as PostgreSQL. >> > > Thanks :) I agree that H2 can't be everything to everyone (and vice versa, > I wouldn't use Postgresql for a self-contained application). > > Gili > > -- > 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/d/optout. > -- 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/d/optout.
