You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Romain Manni-Bucau <rm...@gmail.com> on 2012/07/06 10:40:58 UTC
why do we use hsqldb?
Hi,
why are we using hsqdb by default?
as embedded database i like h2 but there is derby too which is @ apache
any reason?
do we want to switch?
- Romain
Re: why do we use hsqldb?
Posted by Romain Manni-Bucau <rm...@gmail.com>.
all tests, at least mine ;)
- Romain
2012/7/9 Mark Struberg <st...@yahoo.de>
> Well, the default DB is just for samples anyway ;)
>
> No real project is using that stuff I guess ^^
>
>
> LieGrue,
> strub
>
>
>
> ----- Original Message -----
> > From: Romain Manni-Bucau <rm...@gmail.com>
> > To: dev@openejb.apache.org; Mark Struberg <st...@yahoo.de>
> > Cc:
> > Sent: Monday, July 9, 2012 5:28 PM
> > Subject: Re: why do we use hsqldb?
> >
> >t he issue with derbye is it is slow in embedded mode compared to hsqldb
> >
> >
> > - Romain
> >
> >
> > 2012/7/9 Mark Struberg <st...@yahoo.de>
> >
> >> Size is from 0 to 600kB. Derby comes out of the box in JDK5 and 6
> afaik.
> >> Not sure if it's part of JRE though.
> >> Start time should be measured.
> >>
> >> LieGrue,
> >> strub
> >>
> >>
> >>
> >> ----- Original Message -----
> >> > From: David Blevins <da...@gmail.com>
> >> > To: dev@openejb.apache.org
> >> > Cc:
> >> > Sent: Friday, July 6, 2012 5:02 PM
> >> > Subject: Re: why do we use hsqldb?
> >> >
> >> >
> >> > On Jul 6, 2012, at 4:21 AM, Romain Manni-Bucau wrote:
> >> >
> >> >> http://www.h2database.com/html/performance.html
> >> >>
> >> >> that's biased because of the source but derby seems pretty
> > slow which
> >> > is
> >> >> not so fine for tests
> >> >
> >> > Performance & size. We can certainly check it out again.
> >> >
> >> > If it adds even 500ms on the embedded boot time, that'd be too
> > much. Our
> >> > embedded test times have gotten slower. Hopefully something we can
> >> investigate
> >> > more at some point -- I have looked into it a bit.
> >> >
> >> > Test times of injection-of-entitymanager on my machine:
> >> >
> >> > - 4.1.0, 2.459 sec
> >> > - 3.1.4, 1.903 sec
> >> >
> >> > Would hate to see that go up more than it has.
> >> >
> >> >
> >> > -David
> >> >
> >> >> 2012/7/6 AndyG <an...@orprovision.com>
> >> >>
> >> >>> +1 Derby
> >> >>>
> >> >>> Using it for a long time in production.
> >> >>>
> >> >>> --
> >> >>> View this message in context:
> >> >>>
> >> >
> >>
> >
> http://openejb.979440.n4.nabble.com/why-do-we-use-hsqldb-tp4656087p4656098.html
> >> >>> Sent from the OpenEJB Dev mailing list archive at Nabble.com.
> >> >>>
> >> >
> >>
> >
>
Re: why do we use hsqldb?
Posted by Enrico Olivelli <eo...@gmail.com>.
I am using the embeded ActiveMQ for development and sometimes I get the
following error
the only way to resolve my problem is to errse the jmsdata directory
(but I lose all my messages...)
mag 27, 2012 2:23:24 PM
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter loadAdapter
Informazioni: Database adapter driver override recognized for :
[hsql_database_engine_driver] - adapter: class
org.apache.activemq.store.jdbc.adapter.HsqldbJDBCAdapter
mag 27, 2012 2:23:24 PM
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter loadAdapter
Informazioni: Database lock driver override not found for :
[hsql_database_engine_driver]. Will use default implementation.
mag 27, 2012 2:23:24 PM
org.apache.activemq.store.jdbc.DefaultDatabaseLocker start
Informazioni: Attempting to acquire the exclusive lock to become the
Master broker
mag 27, 2012 2:23:24 PM
org.apache.activemq.store.jdbc.DefaultDatabaseLocker start
Informazioni: Becoming the master on dataSource:
org.apache.openejb.resource.jdbc.BasicDataSource@6697828
mag 27, 2012 2:23:24 PM org.apache.activemq.broker.BrokerService getBroker
Informazioni: ActiveMQ 5.5.1 JMS Message Broker (localhost) is starting
mag 27, 2012 2:23:24 PM org.apache.activemq.broker.BrokerService getBroker
Informazioni: For help or more information please see:
http://activemq.apache.org/
mag 27, 2012 2:23:24 PM
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter log
Avvertenza: JDBC Failure: incompatible data type in conversion: from SQL
type OTHER to [B, value: instance of org.hsqldb.types.JavaObjectData
java.sql.SQLSyntaxErrorException: incompatible data type in conversion:
from SQL type OTHER to [B, value: instance of
org.hsqldb.types.JavaObjectData
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.Util.throwError(Unknown Source)
at org.hsqldb.jdbc.JDBCResultSet.getColumnInType(Unknown Source)
at org.hsqldb.jdbc.JDBCResultSet.getBytes(Unknown Source)
at
org.apache.commons.dbcp.DelegatingResultSet.getBytes(DelegatingResultSet.java:241)
at
org.apache.commons.dbcp.DelegatingResultSet.getBytes(DelegatingResultSet.java:241)
at
org.apache.activemq.store.jdbc.adapter.BytesJDBCAdapter.getBinaryData(BytesJDBCAdapter.java:38)
at
org.apache.activemq.store.jdbc.adapter.DefaultJDBCAdapter.doGetMessageById(DefaultJDBCAdapter.java:194)
at
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.getLastMessageBrokerSequenceId(JDBCPersistenceAdapter.java:234)
at
org.apache.activemq.broker.region.DestinationFactoryImpl.getLastMessageBrokerSequenceId(DestinationFactoryImpl.java:145)
at
org.apache.activemq.broker.region.RegionBroker.<init>(RegionBroker.java:122)
at
org.apache.activemq.broker.jmx.ManagedRegionBroker.<init>(ManagedRegionBroker.java:99)
at
org.apache.activemq.broker.BrokerService.createRegionBroker(BrokerService.java:1830)
at
org.apache.activemq.broker.BrokerService.createRegionBroker(BrokerService.java:1824)
at
org.apache.activemq.broker.BrokerService.createBroker(BrokerService.java:1781)
at
org.apache.activemq.broker.BrokerService.getBroker(BrokerService.java:766)
at
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.start(JDBCPersistenceAdapter.java:296)
at
org.apache.activemq.broker.BrokerService.start(BrokerService.java:493)
at
org.apache.openejb.resource.activemq.ActiveMQ5Factory$1.run(ActiveMQ5Factory.java:126)
Caused by: org.hsqldb.HsqlException: incompatible data type in
conversion: from SQL type OTHER to [B, value: instance of
org.hsqldb.types.JavaObjectData
at org.hsqldb.error.Error.error(Unknown Source)
at org.hsqldb.error.Error.error(Unknown Source)
... 17 more
mag 27, 2012 2:23:24 PM org.apache.activemq.broker.BrokerService start
Grave: Failed to start ActiveMQ JMS Message Broker. Reason:
java.io.IOException: Failed to get last broker message id:
java.sql.SQLSyntaxErrorException: incompatible data type in conversion:
from SQL type OTHER to [B, value: instance of
org.hsqldb.types.JavaObjectData
java.io.IOException: Failed to get last broker message id:
java.sql.SQLSyntaxErrorException: incompatible data type in conversion:
from SQL type OTHER to [B, value: instance of
org.hsqldb.types.JavaObjectData
at
org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:33)
at
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.getLastMessageBrokerSequenceId(JDBCPersistenceAdapter.java:245)
at
org.apache.activemq.broker.region.DestinationFactoryImpl.getLastMessageBrokerSequenceId(DestinationFactoryImpl.java:145)
at
org.apache.activemq.broker.region.RegionBroker.<init>(RegionBroker.java:122)
at
org.apache.activemq.broker.jmx.ManagedRegionBroker.<init>(ManagedRegionBroker.java:99)
at
org.apache.activemq.broker.BrokerService.createRegionBroker(BrokerService.java:1830)
at
org.apache.activemq.broker.BrokerService.createRegionBroker(BrokerService.java:1824)
at
org.apache.activemq.broker.BrokerService.createBroker(BrokerService.java:1781)
at
org.apache.activemq.broker.BrokerService.getBroker(BrokerService.java:766)
at
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.start(JDBCPersistenceAdapter.java:296)
at
org.apache.activemq.broker.BrokerService.start(BrokerService.java:493)
at
org.apache.openejb.resource.activemq.ActiveMQ5Factory$1.run(ActiveMQ5Factory.java:126)
Caused by: java.sql.SQLSyntaxErrorException: incompatible data type in
conversion: from SQL type OTHER to [B, value: instance of
org.hsqldb.types.JavaObjectData
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.Util.throwError(Unknown Source)
at org.hsqldb.jdbc.JDBCResultSet.getColumnInType(Unknown Source)
at org.hsqldb.jdbc.JDBCResultSet.getBytes(Unknown Source)
at
org.apache.commons.dbcp.DelegatingResultSet.getBytes(DelegatingResultSet.java:241)
at
org.apache.commons.dbcp.DelegatingResultSet.getBytes(DelegatingResultSet.java:241)
at
org.apache.activemq.store.jdbc.adapter.BytesJDBCAdapter.getBinaryData(BytesJDBCAdapter.java:38)
at
org.apache.activemq.store.jdbc.adapter.DefaultJDBCAdapter.doGetMessageById(DefaultJDBCAdapter.java:194)
at
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.getLastMessageBrokerSequenceId(JDBCPersistenceAdapter.java:234)
... 10 more
Caused by: org.hsqldb.HsqlException: incompatible data type in
conversion: from SQL type OTHER to [B, value: instance of
org.hsqldb.types.JavaObjectData
at org.hsqldb.error.Error.error(Unknown Source)
at org.hsqldb.error.Error.error(Unknown Source)
... 17 more
mag 27, 2012 2:23:24 PM org.apache.activemq.broker.BrokerService stop
Informazioni: ActiveMQ Message Broker (localhost, null) is shutting down
mag 27, 2012 2:23:24 PM org.apache.activemq.broker.TransportConnector stop
Informazioni: Connector null Stopped
mag 27, 2012 2:23:24 PM org.apache.activemq.broker.BrokerService stop
Informazioni: ActiveMQ JMS Message Broker (localhost, null) stopped
mag 27, 2012 2:23:24 PM
org.apache.openejb.resource.activemq.ActiveMQ5Factory createBroker
Grave: ActiveMQ failed to start broker
java.io.IOException: Failed to get last broker message id:
java.sql.SQLSyntaxErrorException: incompatible data type in conversion:
from SQL type OTHER to [B, value: instance of
org.hsqldb.types.JavaObjectData
at
org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:33)
at
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.getLastMessageBrokerSequenceId(JDBCPersistenceAdapter.java:245)
at
org.apache.activemq.broker.region.DestinationFactoryImpl.getLastMessageBrokerSequenceId(DestinationFactoryImpl.java:145)
at
org.apache.activemq.broker.region.RegionBroker.<init>(RegionBroker.java:122)
at
org.apache.activemq.broker.jmx.ManagedRegionBroker.<init>(ManagedRegionBroker.java:99)
at
org.apache.activemq.broker.BrokerService.createRegionBroker(BrokerService.java:1830)
at
org.apache.activemq.broker.BrokerService.createRegionBroker(BrokerService.java:1824)
at
org.apache.activemq.broker.BrokerService.createBroker(BrokerService.java:1781)
at
org.apache.activemq.broker.BrokerService.getBroker(BrokerService.java:766)
at
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.start(JDBCPersistenceAdapter.java:296)
at
org.apache.activemq.broker.BrokerService.start(BrokerService.java:493)
at
org.apache.openejb.resource.activemq.ActiveMQ5Factory$1.run(ActiveMQ5Factory.java:126)
Caused by: java.sql.SQLSyntaxErrorException: incompatible data type in
conversion: from SQL type OTHER to [B, value: instance of
org.hsqldb.types.JavaObjectData
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.Util.throwError(Unknown Source)
at org.hsqldb.jdbc.JDBCResultSet.getColumnInType(Unknown Source)
at org.hsqldb.jdbc.JDBCResultSet.getBytes(Unknown Source)
at
org.apache.commons.dbcp.DelegatingResultSet.getBytes(DelegatingResultSet.java:241)
at
org.apache.commons.dbcp.DelegatingResultSet.getBytes(DelegatingResultSet.java:241)
at
org.apache.activemq.store.jdbc.adapter.BytesJDBCAdapter.getBinaryData(BytesJDBCAdapter.java:38)
at
org.apache.activemq.store.jdbc.adapter.DefaultJDBCAdapter.doGetMessageById(DefaultJDBCAdapter.java:194)
at
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.getLastMessageBrokerSequenceId(JDBCPersistenceAdapter.java:234)
... 10 more
Caused by: org.hsqldb.HsqlException: incompatible data type in
conversion: from SQL type OTHER to [B, value: instance of
org.hsqldb.types.JavaObjectData
at org.hsqldb.error.Error.error(Unknown Source)
at org.hsqldb.error.Error.error(Unknown Source)
... 17 more
Il 09/07/2012 22:12, Mark Struberg ha scritto:
> Well, the default DB is just for samples anyway ;)
>
> No real project is using that stuff I guess ^^
>
>
> LieGrue,
> strub
>
>
>
> ----- Original Message -----
>> From: Romain Manni-Bucau <rm...@gmail.com>
>> To: dev@openejb.apache.org; Mark Struberg <st...@yahoo.de>
>> Cc:
>> Sent: Monday, July 9, 2012 5:28 PM
>> Subject: Re: why do we use hsqldb?
>>
>> t he issue with derbye is it is slow in embedded mode compared to hsqldb
>>
>>
>> - Romain
>>
>>
>> 2012/7/9 Mark Struberg <st...@yahoo.de>
>>
>>> Size is from 0 to 600kB. Derby comes out of the box in JDK5 and 6 afaik.
>>> Not sure if it's part of JRE though.
>>> Start time should be measured.
>>>
>>> LieGrue,
>>> strub
>>>
>>>
>>>
>>> ----- Original Message -----
>>> > From: David Blevins <da...@gmail.com>
>>> > To: dev@openejb.apache.org
>>> > Cc:
>>> > Sent: Friday, July 6, 2012 5:02 PM
>>> > Subject: Re: why do we use hsqldb?
>>> >
>>> >
>>> > On Jul 6, 2012, at 4:21 AM, Romain Manni-Bucau wrote:
>>> >
>>> >> http://www.h2database.com/html/performance.html
>>> >>
>>> >> that's biased because of the source but derby seems pretty
>> slow which
>>> > is
>>> >> not so fine for tests
>>> >
>>> > Performance & size. We can certainly check it out again.
>>> >
>>> > If it adds even 500ms on the embedded boot time, that'd be too
>> much. Our
>>> > embedded test times have gotten slower. Hopefully something we can
>>> investigate
>>> > more at some point -- I have looked into it a bit.
>>> >
>>> > Test times of injection-of-entitymanager on my machine:
>>> >
>>> > - 4.1.0, 2.459 sec
>>> > - 3.1.4, 1.903 sec
>>> >
>>> > Would hate to see that go up more than it has.
>>> >
>>> >
>>> > -David
>>> >
>>> >> 2012/7/6 AndyG <an...@orprovision.com>
>>> >>
>>> >>> +1 Derby
>>> >>>
>>> >>> Using it for a long time in production.
>>> >>>
>>> >>> --
>>> >>> View this message in context:
>>> >>>
>>> >
>>>
>> http://openejb.979440.n4.nabble.com/why-do-we-use-hsqldb-tp4656087p4656098.html
>>> >>> Sent from the OpenEJB Dev mailing list archive at Nabble.com.
>>> >>>
>>> >
>>>
Re: why do we use hsqldb?
Posted by Mark Struberg <st...@yahoo.de>.
Well, the default DB is just for samples anyway ;)
No real project is using that stuff I guess ^^
LieGrue,
strub
----- Original Message -----
> From: Romain Manni-Bucau <rm...@gmail.com>
> To: dev@openejb.apache.org; Mark Struberg <st...@yahoo.de>
> Cc:
> Sent: Monday, July 9, 2012 5:28 PM
> Subject: Re: why do we use hsqldb?
>
>t he issue with derbye is it is slow in embedded mode compared to hsqldb
>
>
> - Romain
>
>
> 2012/7/9 Mark Struberg <st...@yahoo.de>
>
>> Size is from 0 to 600kB. Derby comes out of the box in JDK5 and 6 afaik.
>> Not sure if it's part of JRE though.
>> Start time should be measured.
>>
>> LieGrue,
>> strub
>>
>>
>>
>> ----- Original Message -----
>> > From: David Blevins <da...@gmail.com>
>> > To: dev@openejb.apache.org
>> > Cc:
>> > Sent: Friday, July 6, 2012 5:02 PM
>> > Subject: Re: why do we use hsqldb?
>> >
>> >
>> > On Jul 6, 2012, at 4:21 AM, Romain Manni-Bucau wrote:
>> >
>> >> http://www.h2database.com/html/performance.html
>> >>
>> >> that's biased because of the source but derby seems pretty
> slow which
>> > is
>> >> not so fine for tests
>> >
>> > Performance & size. We can certainly check it out again.
>> >
>> > If it adds even 500ms on the embedded boot time, that'd be too
> much. Our
>> > embedded test times have gotten slower. Hopefully something we can
>> investigate
>> > more at some point -- I have looked into it a bit.
>> >
>> > Test times of injection-of-entitymanager on my machine:
>> >
>> > - 4.1.0, 2.459 sec
>> > - 3.1.4, 1.903 sec
>> >
>> > Would hate to see that go up more than it has.
>> >
>> >
>> > -David
>> >
>> >> 2012/7/6 AndyG <an...@orprovision.com>
>> >>
>> >>> +1 Derby
>> >>>
>> >>> Using it for a long time in production.
>> >>>
>> >>> --
>> >>> View this message in context:
>> >>>
>> >
>>
> http://openejb.979440.n4.nabble.com/why-do-we-use-hsqldb-tp4656087p4656098.html
>> >>> Sent from the OpenEJB Dev mailing list archive at Nabble.com.
>> >>>
>> >
>>
>
Re: why do we use hsqldb?
Posted by Romain Manni-Bucau <rm...@gmail.com>.
the issue with derbye is it is slow in embedded mode compared to hsqldb
- Romain
2012/7/9 Mark Struberg <st...@yahoo.de>
> Size is from 0 to 600kB. Derby comes out of the box in JDK5 and 6 afaik.
> Not sure if it's part of JRE though.
> Start time should be measured.
>
> LieGrue,
> strub
>
>
>
> ----- Original Message -----
> > From: David Blevins <da...@gmail.com>
> > To: dev@openejb.apache.org
> > Cc:
> > Sent: Friday, July 6, 2012 5:02 PM
> > Subject: Re: why do we use hsqldb?
> >
> >
> > On Jul 6, 2012, at 4:21 AM, Romain Manni-Bucau wrote:
> >
> >> http://www.h2database.com/html/performance.html
> >>
> >> that's biased because of the source but derby seems pretty slow which
> > is
> >> not so fine for tests
> >
> > Performance & size. We can certainly check it out again.
> >
> > If it adds even 500ms on the embedded boot time, that'd be too much. Our
> > embedded test times have gotten slower. Hopefully something we can
> investigate
> > more at some point -- I have looked into it a bit.
> >
> > Test times of injection-of-entitymanager on my machine:
> >
> > - 4.1.0, 2.459 sec
> > - 3.1.4, 1.903 sec
> >
> > Would hate to see that go up more than it has.
> >
> >
> > -David
> >
> >> 2012/7/6 AndyG <an...@orprovision.com>
> >>
> >>> +1 Derby
> >>>
> >>> Using it for a long time in production.
> >>>
> >>> --
> >>> View this message in context:
> >>>
> >
> http://openejb.979440.n4.nabble.com/why-do-we-use-hsqldb-tp4656087p4656098.html
> >>> Sent from the OpenEJB Dev mailing list archive at Nabble.com.
> >>>
> >
>
Re: why do we use hsqldb?
Posted by Mark Struberg <st...@yahoo.de>.
Size is from 0 to 600kB. Derby comes out of the box in JDK5 and 6 afaik. Not sure if it's part of JRE though.
Start time should be measured.
LieGrue,
strub
----- Original Message -----
> From: David Blevins <da...@gmail.com>
> To: dev@openejb.apache.org
> Cc:
> Sent: Friday, July 6, 2012 5:02 PM
> Subject: Re: why do we use hsqldb?
>
>
> On Jul 6, 2012, at 4:21 AM, Romain Manni-Bucau wrote:
>
>> http://www.h2database.com/html/performance.html
>>
>> that's biased because of the source but derby seems pretty slow which
> is
>> not so fine for tests
>
> Performance & size. We can certainly check it out again.
>
> If it adds even 500ms on the embedded boot time, that'd be too much. Our
> embedded test times have gotten slower. Hopefully something we can investigate
> more at some point -- I have looked into it a bit.
>
> Test times of injection-of-entitymanager on my machine:
>
> - 4.1.0, 2.459 sec
> - 3.1.4, 1.903 sec
>
> Would hate to see that go up more than it has.
>
>
> -David
>
>> 2012/7/6 AndyG <an...@orprovision.com>
>>
>>> +1 Derby
>>>
>>> Using it for a long time in production.
>>>
>>> --
>>> View this message in context:
>>>
> http://openejb.979440.n4.nabble.com/why-do-we-use-hsqldb-tp4656087p4656098.html
>>> Sent from the OpenEJB Dev mailing list archive at Nabble.com.
>>>
>
Re: why do we use hsqldb?
Posted by David Blevins <da...@gmail.com>.
On Jul 6, 2012, at 4:21 AM, Romain Manni-Bucau wrote:
> http://www.h2database.com/html/performance.html
>
> that's biased because of the source but derby seems pretty slow which is
> not so fine for tests
Performance & size. We can certainly check it out again.
If it adds even 500ms on the embedded boot time, that'd be too much. Our embedded test times have gotten slower. Hopefully something we can investigate more at some point -- I have looked into it a bit.
Test times of injection-of-entitymanager on my machine:
- 4.1.0, 2.459 sec
- 3.1.4, 1.903 sec
Would hate to see that go up more than it has.
-David
> 2012/7/6 AndyG <an...@orprovision.com>
>
>> +1 Derby
>>
>> Using it for a long time in production.
>>
>> --
>> View this message in context:
>> http://openejb.979440.n4.nabble.com/why-do-we-use-hsqldb-tp4656087p4656098.html
>> Sent from the OpenEJB Dev mailing list archive at Nabble.com.
>>
Re: why do we use hsqldb?
Posted by Romain Manni-Bucau <rm...@gmail.com>.
another drawback of derby is it is huge :(
- Romain
2012/7/6 Jean-Louis MONTEIRO <je...@gmail.com>
> +1 for Derby
>
> 2012/7/6 Romain Manni-Bucau <rm...@gmail.com>
>
> > http://www.h2database.com/html/performance.html
> >
> > that's biased because of the source but derby seems pretty slow which is
> > not so fine for tests
> >
> > thoughts?
> >
> > - Romain
> >
> >
> > 2012/7/6 AndyG <an...@orprovision.com>
> >
> > > +1 Derby
> > >
> > > Using it for a long time in production.
> > >
> > > --
> > > View this message in context:
> > >
> >
> http://openejb.979440.n4.nabble.com/why-do-we-use-hsqldb-tp4656087p4656098.html
> > > Sent from the OpenEJB Dev mailing list archive at Nabble.com.
> > >
> >
>
Re: why do we use hsqldb?
Posted by Jean-Louis MONTEIRO <je...@gmail.com>.
+1 for Derby
2012/7/6 Romain Manni-Bucau <rm...@gmail.com>
> http://www.h2database.com/html/performance.html
>
> that's biased because of the source but derby seems pretty slow which is
> not so fine for tests
>
> thoughts?
>
> - Romain
>
>
> 2012/7/6 AndyG <an...@orprovision.com>
>
> > +1 Derby
> >
> > Using it for a long time in production.
> >
> > --
> > View this message in context:
> >
> http://openejb.979440.n4.nabble.com/why-do-we-use-hsqldb-tp4656087p4656098.html
> > Sent from the OpenEJB Dev mailing list archive at Nabble.com.
> >
>
Re: why do we use hsqldb?
Posted by AndyG <an...@orprovision.com>.
I'd like to see the results with a more recent release as that test is over 2
years old
--
View this message in context: http://openejb.979440.n4.nabble.com/why-do-we-use-hsqldb-tp4656087p4656201.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: why do we use hsqldb?
Posted by Romain Manni-Bucau <rm...@gmail.com>.
http://www.h2database.com/html/performance.html
that's biased because of the source but derby seems pretty slow which is
not so fine for tests
thoughts?
- Romain
2012/7/6 AndyG <an...@orprovision.com>
> +1 Derby
>
> Using it for a long time in production.
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/why-do-we-use-hsqldb-tp4656087p4656098.html
> Sent from the OpenEJB Dev mailing list archive at Nabble.com.
>
Re: why do we use hsqldb?
Posted by AndyG <an...@orprovision.com>.
+1 Derby
Using it for a long time in production.
--
View this message in context: http://openejb.979440.n4.nabble.com/why-do-we-use-hsqldb-tp4656087p4656098.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: why do we use hsqldb?
Posted by Romain Manni-Bucau <rm...@gmail.com>.
any feedback on perfs?
- Romain
2012/7/6 Mark Struberg <st...@yahoo.de>
> +1 for derby as it comes with java
>
>
> LieGrue,
> strub
>
>
>
> ----- Original Message -----
> > From: Romain Manni-Bucau <rm...@gmail.com>
> > To: dev@openejb.apache.org
> > Cc:
> > Sent: Friday, July 6, 2012 10:40 AM
> > Subject: why do we use hsqldb?
> >
> > Hi,
> >
> > why are we using hsqdb by default?
> >
> > as embedded database i like h2 but there is derby too which is @ apache
> >
> > any reason?
> >
> > do we want to switch?
> >
> > - Romain
> >
>
Re: why do we use hsqldb?
Posted by Mark Struberg <st...@yahoo.de>.
+1 for derby as it comes with java
LieGrue,
strub
----- Original Message -----
> From: Romain Manni-Bucau <rm...@gmail.com>
> To: dev@openejb.apache.org
> Cc:
> Sent: Friday, July 6, 2012 10:40 AM
> Subject: why do we use hsqldb?
>
> Hi,
>
> why are we using hsqdb by default?
>
> as embedded database i like h2 but there is derby too which is @ apache
>
> any reason?
>
> do we want to switch?
>
> - Romain
>