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 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 been for two years now, with a few thousand users. The Derby DB is
more
of a thick-client local cache of a subset of the real DB (which is DB/2),
but
those embedded databases are managing hundreds of megs of data and we've
never seen a single DB-related issue.
Shawn.
_______________________________________________
Ldsoss mailing list
Ldsoss@lists.ldsoss.org
http://lists.ldsoss.org/mailman/listinfo/ldsoss
_______________________________________________
Ldsoss mailing list
Ldsoss@lists.ldsoss.org
http://lists.ldsoss.org/mailman/listinfo/ldsoss
