>> How many times were you hit by a database corruption and couldn't recover any data at all?
never! I have never not been able to recover data. I use H2 on a 24/7 sever system, and never had a corruption for years. However, I do have a solid backup strategy in place so I am not too concerned if the DB gets corrupted: no one will lose life or job. >>How many releases of H2 were tagged as stable and not as alpha/beta? I think most databases have the same alpha/beta/stable release cycle. >>Not matter how much I personally love using H2 for personal or professional projects, these 2 questions above always pop up in the mind of my team members. To them robustness is an issue with H2. I agree. Luckily I don't have people breathing down my neck, but I think it would be hard to justify using H2 when it is not seen as being an "enterprise" solution. >>And it's the same with us, fervent users: we always look forward to the next release of H2, it's hard for us to tell which specific release was good enough in terms of speed and stability. I tend to agree, but I am using an older 1.3x stable version and have not upgraded. Why? because it works and I don't want to risk it with a newer version. If it works, don't change it (or at least for my situation. -Adam On Wednesday, March 7, 2018 at 2:46:05 AM UTC-5, Christian MICHON wrote: > > How many times were you hit by a database corruption and couldn't recover > any data at all? > How many releases of H2 were tagged as stable and not as alpha/beta? > > Not matter how much I personally love using H2 for personal or > professional projects, these 2 questions above always pop up in the mind of > my team members. To them robustness is an issue with H2. > > And it's the same with us, fervent users: we always look forward to the > next release of H2, it's hard for us to tell which specific release was > good enough in terms of speed and stability. > > On Wednesday, March 7, 2018 at 4:46:43 AM UTC+1, Adam McMahon wrote: >> >> Redhat has a warning about H2 in several places in their docs. >> >> The H2 database should *not* be used in a production environment. This >> is a very small, self-contained datasource that supports all of the >> standards needed for testing and building applications, but is not robust >> or scalable enough for production use. >> >> >> https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.1/html/configuration_guide/datasource_management >> >> I find this warning to be a little odd. Perhaps RedHat is just trying to >> cover themselves legally. Any ideas what aspects of H2 they might be >> referring to? They mention 2 categories : >> >> *robust*: not sure what they mean in this context >> *scalable* : I would agree with them here, if by scalable they mean >> having a bulit-in ability to horizontally scale across several machines. >> >> -Adam >> > -- 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 post to this group, send email to h2-database@googlegroups.com. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
