Bruce Snyder wrote:
> > Why not use HSQL as test database?
> > Setting up this database is really very simple, and compatible to any
> > environment, because it is a pure Java solution.
> I don't mind using either one. I use all kinds of different databases
> for development. But if we're going to think about using HSQL, then I
> think we should definitely consider using Derby.
[...]
> As a third choice, I think we should also consider using Derby. Derby is
> also embeddable like HSQL, is 100% pure Java, but Derby is *far, far*
> more powerful and supports all tx isolation levels:
Well, I don't think it is that important to have available all this isolation
levels for example programs. (at least not for simple ones) This is something,
which is important if you want to use an application in a multi user
environment.
But of course I also don't mind using a superior DB like Derby/Cloudscape if
it's comparable simple to install as HSQL.
> > We could even provide a pre-packaged template to make it quite easy
> > for users integrating their examples.
> As far as a template goes, do we really want to restrict all entries in
> the contest to a particular set of tables? I don't think I'm in favor of
> that. However, I am in favor of placing a limit on the size of the
> application in some way.
I didn't think of restricting contributions to only one database schema.
One should be able to use any tables, he/she needs. However placing
a simple example schema like that of our CTF as default in the template
would not hurt. It can be altered, extended, or even replaced by a completely
different to fullfill the specific needs.
Regards,
Martin
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-user
