MySQL and h2 are more relevant for prod but h2 was not bringing added value to hsqldb which was here for ears and was a bit qlower IIRC. MySQL is not embeddable in a portable manner. Le 26 juil. 2013 20:35, "Howard W. Smith, Jr." <[email protected]> a écrit :
> Is there any reason why mysql or h2 was not selected? > > I do see more questions and issues about/related-to mysql on this list. > While that might be a reason why mysql was not selected, it most likely > means many tomee users are using mysql. :-) > > I don't think I've seen anyone mention any questions or issues on this list > about h2. Earlier, others on this list advised me to use mysql or h2 > instead of Derby. > On Jul 26, 2013 5:08 AM, "Romain Manni-Bucau" <[email protected]> > wrote: > > > Hi > > > > We discussed it on dev list and we ship the same db in openejb and tomee > > and derby is slower than hsqldb which is nit acceptable for tests. > > Le 26 juil. 2013 05:10, "Howard W. Smith, Jr." <[email protected]> > a > > écrit : > > > > > Interesting question. Maybe it has something to do with the fact that > > > Apache Derby (Java DB) is shipped with Glassfish. :) > > > > > > Since I started as a Glassfish 3.1.x user, Apache Derby was what I > > > initially used when I developed my database and JSF web app via > Glassfish > > > and Derby, and still using Derby with TomEE, even though others advised > > > against it. > > > > > > Looking forward to the committers' response to this one. :) > > > > > > > > > > > > On Thu, Jul 25, 2013 at 11:00 PM, jieryn <[email protected]> wrote: > > > > > > > Greetings, > > > > > > > > Why does TomEE embed HSQLDB instead of Apache Derby? > > > > > > > > I expected that we'd default to an Apache project instead of a 3rd > > > > party. Is there some major malfunction with Apache Derby? > > > > > > > > > >
