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
> will be viable over the next 5+ years or is portable enough to be easily
> migrated
>
>
> HTH
>
> -G
>
> > -Original Message-
> > From: David Leader [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, October 30, 2007 2:54 PM
> > To: Derby Disc
and C#?
Does this make sense?
As an "early" adopter, you're taking a risk that your platform/technology
will be viable over the next 5+ years or is portable enough to be easily
migrated
HTH
-G
> -Original Message-
> From: David Leader [mailto:[EMAIL PROTECTED]
In another thread I recently wrote "I'm happy with the way that Derby
has behaved, but I'd like to ask a provocative question nevertheless..."
Back in the summer, when I told my son (who is a computer
professional) that I had a Masters student porting my MySQL db to
Derby, he told me I shou
