Very nice! Is Java DB embedded in the applet, or used solely on the
server side?
David
On Oct 31, 2007 2:41 PM, David Leader <[EMAIL PROTECTED]> wrote:
> I found the replies to my query interesting. I guess I need to ask my
> son why he favours SQLite. I much prefer to stick with a Java-based
>
I found the replies to my query interesting. I guess I need to ask my
son why he favours SQLite. I much prefer to stick with a Java-based
solution as writing academic software on the Mac it has to be cross-
platform, and I was unaware - and found it heartening - that Sun's
JavaDB was an impl
Personally, I think there's no comparison between Derby and SQLite.
Derby's an actual database with "all" the bells and whistles, but still
a really compact size. SQLite is an extremely fast database-like system
with a much smaller subset of features and SQL compliance. Plus, if
you're writing in J
David,
Gears is a client side framework for web applications. If you have a Java
application (be it client standalone, web or server) and you want to embed a
database system and be able to port it across platforms, Derby makes a lot
of sense (being 100% Java); It has a strong and active developmen
There are a couple of issues raised by your post/email...
First the architecture decision on whether to use a java db or to use a c
language based db. You don't really talk about your application and any
design constraints. In some respects, the database could be separate from
your app. (A centra
