tag:blogger.com,1999:blog-15929719.post611270723661881674..comments2023-10-21T01:56:53.775-07:00Comments on Van Couvering Is Not a Verb: Derby vs. SQLite - one user chimes inAnonymoushttp://www.blogger.com/profile/04898259486137280102noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-15929719.post-47230925184188479432009-04-11T09:27:00.000-07:002009-04-11T09:27:00.000-07:00This week I had a cool essay on Java / Derby . I h...This week I had a cool essay on Java / Derby . I haven't used Derby before . I start orgininizing my efforts with my similaro knowledge on MySql , MsSql etc ...<BR/><BR/>After 2-3 days I found some MAJOR limitations of Derby:<BR/><BR/>Derby (until its current v 10.5) does not support something like 'select top xx' thing (Yes the standard answer 'You can do that from Java') but what if I want to use 3-4 sub selects with 'select top xx'<BR/><BR/>Derby cannot save a view if there's is an 'order by' !!<BR/><BR/>Actuall Derby cannot have a sub select with 'order by' .<BR/><BR/>After all theese I went straight to Sqlite to see if i had those limitations ... unbelievable ... Sqlite have none of the above obstacles .<BR/><BR/>I start thinking that all these guys talking about Derby , didn't seriously used it .<BR/><BR/>Ms Access 95 (!) , or 250KB Sqlite have some more capabilities of Derby !.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-15929719.post-75509400620137429672007-11-03T08:57:00.000-07:002007-11-03T08:57:00.000-07:00For Java applications I'd rather choose H2 databas...For Java applications I'd rather choose H2 database or even HSQLDB instead of Derby for many reasons including support of in-memory mode for testing.<BR/>I don't want to say that Derby is worse than H2, but it is slower in most cases and H2 is lighter in memory footprint and JAR size.MF Joneshttps://www.blogger.com/profile/11509082735402966975noreply@blogger.com