FYI I believe that you'll find JavaDB available from Sun which is supposedly
Sun's name for Derby.
So, if you are confused and see JavaDB it's actually Derby.
-Clint
On 5/15/07, Shawn Willden <[EMAIL PROTECTED]> wrote:
On Tuesday 15 May 2007 12:56:05 pm David Hale wrote:
> It may just be my g
On Tuesday 15 May 2007 12:56:05 pm David Hale wrote:
> It may just be my gut feel, but I would probably only use Derby for
> a "development" database rather than to depend on it for a "production"
> environment.
My current project (at work) is using embedded Derby for production work, and
has be
On Tuesday 15 May 2007 01:19:39 pm John Finlay wrote:
> If you use something like JPA and Hibernate you can allow users to setup
> the client with their favorite DB through a simple configuration file.
Absolutely. I think this is a really big advantage of using an abstraction
layer like JPA/Hibe
platforms and programs who do not intend to adopt the web
service API)
--John
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Finlay
Sent: Tuesday, May 15, 2007 9:53 AM
To: LDS Open Source Software
Subject: RE: [Ldsoss] Database for FamilySearch OpenSource Client
I've
May 15, 2007 9:53:21 AM
Subject: RE: [Ldsoss] Database for FamilySearch OpenSource Client
p.MsoNormal
{margin-left:3.0pt;}
I’ve used Derby and HSQL. Both are good embeddable
DBs. It sounds like H2 is worth looking into though.
For a database abstraction framework, I
On Tuesday 15 May 2007 09:23:45 am Steven H. McCown wrote:
> I'll second those with my emphasis being on Derby. With all the OSing that
> Sun is doing is the Derby source available?
Derby isn't from Sun, it's from IBM (original name was Cloudscape). And, yes,
source is available, under the Apac
I've used Derby and HSQL. Both are good embeddable DBs. It sounds like
H2 is worth looking into though.
For a database abstraction framework, I would go with the new standard
Java Persistence API (JPA). With the JPA and Java 5's annotations and
generics, developing a persistence layer is a bree
You are right. I did not notice it but I went back to the original
message and it shows June 15 as the date.
Tom
John M. Shaw wrote:
Did anyone else see Gordon's message come through with a date of June
15, 2007?
- Original Message
From: Gordon Clarke <[EMAIL PROTECTED]>
To: LDSOSS
Did anyone else see Gordon's message come through with a date of June 15, 2007?
- Original Message
From: Gordon Clarke <[EMAIL PROTECTED]>
To: LDSOSS@LISTS.LDSOSS.ORG
Sent: Friday, June 15, 2007 9:51:04 AM
Subject: [Ldsoss] Database for FamilySearch OpenSource Client
LDS Developers,
On Friday 15 June 2007 08:51:04 am Gordon Clarke wrote:
> 3) What do you think about the Derby? H2?
I've used Derby extensively as an embedded database, with Hibernate to do OO
mapping. I found it to be fast, bug-free and very easy to work with.
I haven't used H2.
Shawn.
t: Re: [Ldsoss] Database for FamilySearch OpenSource Client
I've used both Derby and H2 and find H2 much faster, easier to use, fault
tolerant, and light weight. If you are looking for a great embedded DB, I'd
recommend H2. Their code can run in client-server mode but I've not used
I've used both Derby and H2 and find H2 much faster, easier to use,
fault tolerant, and light weight. If you are looking for a great
embedded DB, I'd recommend H2. Their code can run in client-server mode
but I've not used it in that way.
Tom
Gordon Clarke wrote:
LDS Developers,
I have t
12 matches
Mail list logo
