You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by jieryn <ji...@gmail.com> on 2013/07/26 05:00:05 UTC
TomEE: Apache Derby vs HSQLDB
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?
Re: TomEE: Apache Derby vs HSQLDB
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
+1, agreed 100%, and thanks, AndyG.
Derby = Apache, and within the last 1 to 2 years, I have selected to use
more Apache open source libraries/software...and you surely don't see me
complaining. :)
On Mon, Jul 29, 2013 at 4:57 AM, AndyG <an...@orprovision.com>wrote:
> The choice is open for you to use just about any JDBC supported database.
>
> Personally I am using (and have used for several years) Derby for an
> embedded mode application and PostgreSQL for a remote version of the same
> application. Both have proven to be extremely stable in production.
>
> Andy.
>
>
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/TomEE-Apache-Derby-vs-HSQLDB-tp4664362p4664415.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>
Re: TomEE: Apache Derby vs HSQLDB
Posted by AndyG <an...@orprovision.com>.
The choice is open for you to use just about any JDBC supported database.
Personally I am using (and have used for several years) Derby for an
embedded mode application and PostgreSQL for a remote version of the same
application. Both have proven to be extremely stable in production.
Andy.
--
View this message in context: http://openejb.979440.n4.nabble.com/TomEE-Apache-Derby-vs-HSQLDB-tp4664362p4664415.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: TomEE: Apache Derby vs HSQLDB
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
interesting...thanks for the response, Romain...as always! :)
On Fri, Jul 26, 2013 at 2:49 PM, Romain Manni-Bucau
<rm...@gmail.com>wrote:
> 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." <sm...@gmail.com> 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" <rm...@gmail.com>
> > 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." <smithh032772@gmail.com
> >
> > 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 <ji...@gmail.com> 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?
> > > > >
> > > >
> > >
> >
>
Re: TomEE: Apache Derby vs HSQLDB
Posted by Romain Manni-Bucau <rm...@gmail.com>.
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." <sm...@gmail.com> 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" <rm...@gmail.com>
> 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." <sm...@gmail.com>
> 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 <ji...@gmail.com> 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?
> > > >
> > >
> >
>
Re: TomEE: Apache Derby vs HSQLDB
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
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" <rm...@gmail.com> 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." <sm...@gmail.com> 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 <ji...@gmail.com> 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?
> > >
> >
>
Re: TomEE: Apache Derby vs HSQLDB
Posted by Ron Smits <ro...@gmail.com>.
What manner of performance difference is there? Just a ballpark figure
would be nice :)
I am asking this as I use derby a lot too, and find it a very good and
stable db.
Ron
I Haven't Lost My Mind - It's Backed Up On Disk Somewhere
On Mon, Aug 5, 2013 at 5:37 PM, jieryn <ji...@gmail.com> wrote:
> Greetings,
>
> On Fri, Jul 26, 2013 at 1:08 AM, Romain Manni-Bucau
> <rm...@gmail.com> wrote:
> > 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.
>
> I'm not immune to that kind of argument, I think things should be very
> easy/fast to build and test for developers. It's just that I am
> listening to David Blevins talk about how TomEE uses all Apache
> componentry [1] and it is intentional and also something which is
> generally a Good Thing.
>
> I think the TomEE 2.x series would be a natural place to
> re-investigate using all Apache components again.
>
> [1]
> http://jaxenter.com/apache-tomee-javaee-6-web-profile-on-tomcat-47873.html
>
Re: TomEE: Apache Derby vs HSQLDB
Posted by jieryn <ji...@gmail.com>.
Greetings,
On Fri, Jul 26, 2013 at 1:08 AM, Romain Manni-Bucau
<rm...@gmail.com> wrote:
> 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.
I'm not immune to that kind of argument, I think things should be very
easy/fast to build and test for developers. It's just that I am
listening to David Blevins talk about how TomEE uses all Apache
componentry [1] and it is intentional and also something which is
generally a Good Thing.
I think the TomEE 2.x series would be a natural place to
re-investigate using all Apache components again.
[1] http://jaxenter.com/apache-tomee-javaee-6-web-profile-on-tomcat-47873.html
Re: TomEE: Apache Derby vs HSQLDB
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
Interesting.
On Jul 26, 2013 1:08 AM, "Romain Manni-Bucau" <rm...@gmail.com>
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." <sm...@gmail.com> 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 <ji...@gmail.com> 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?
> > >
> >
>
Re: TomEE: Apache Derby vs HSQLDB
Posted by Romain Manni-Bucau <rm...@gmail.com>.
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." <sm...@gmail.com> 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 <ji...@gmail.com> 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?
> >
>
Re: TomEE: Apache Derby vs HSQLDB
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
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 <ji...@gmail.com> 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?
>