> I agree with bryan, I would rather see the Derby project concentrate on
> the stated goals of the project as Bryan enumerates.
Derby should live upto its stated goals. But , a large no: of the
users use derby as a simple embedded datastore
Those users
 * Do not care about JDBC compliance
 * Care about footprint jar size and RAM. If I am distributing my
small desktop app I would prefer a smaller jar minimal memory
footprint.
 * They may prefer Derby because it has a very stable, tested codebase
>
-
--Noble Paul

Reply via email to