The future of Java
in [Java Programming]
|
From: Arne Vajhøj on 22 Nov 2009 22:05 Arne Vajh�j wrote: > Roedy Green wrote: >> On Sat, 21 Nov 2009 18:59:04 +0000 (UTC), Martin Gregorie >> <martin(a)address-in-sig.invalid> wrote, quoted or indirectly quoted >> someone who said : >>> How do you rate H2 against Derby and HSQL? >> >> For a comparison of PosGreSQL and MySQL see >> http://mindprod.com/jgloss/postgresql.html >> >> The information is a few years old. > > #PostGres has many data types. > > Most databases has. > > #You can write triggers in Oracle stored procedure language PL/SQL or in > other languages such as Java. > > http://www.postgresql.org/docs/8.2/interactive/triggers.html > > does not list Java but several other languages. > > And even though PL/pgSQL is very similar to Oracle PL/SQL, then > I assume that Oracle prefer it not to be called Oracle PL/SQL. > > > I understand that Derby is fast, but ram resident only. > > Not true. > > > It is for > > small databases only. > > Probably. I forgot: #PostGres does not crash under heavy loads. No databases are supposed to do that. Arne
From: Arne Vajhøj on 22 Nov 2009 22:10 Martin Gregorie wrote: > On Sun, 22 Nov 2009 15:10:32 -0800, Roedy Green wrote: >> On Sat, 21 Nov 2009 18:59:04 +0000 (UTC), Martin Gregorie >> <martin(a)address-in-sig.invalid> wrote, quoted or indirectly quoted >> someone who said : >> >>> How do you rate H2 against Derby and HSQL? >> For a comparison of PosGreSQL and MySQL see >> http://mindprod.com/jgloss/postgresql.html >> >> The information is a few years old. >> >> I understand that Derby is fast, but ram resident only. It is for small >> databases only. >> > I'm interested finding out if Derby, H2 or HSQL could be used as a > lighter weight, portable alternative to PostgreSQL, i.e. minimal changes > to SQL queries and schema, full ACID capability, capable of dealing with > fairly large tables on disk. > > From what you say it looks like Derby wouldn't fit the bill. They are relative similar in target usage. I would go for Derby (Java DB), because: - it comes with newer Java - Informix/IBM/ASF some indicates a certain quality Arne
From: Arne Vajhøj on 22 Nov 2009 22:14 Lew wrote: > Roedy Green wrote: >>> Even if they are swallowed in the blender, I would like to publicly >>> thank them their part in providing me Java, MySQL and Open Office. > > Arne Vajhøj wrote: >> SUN did not provide you MySQL. SUN just acquired the company >> not long ago. And have lost most of the original people since then. > > Small loss. > > I rate MySQL far, far below Postgres, Derby and the free versions of > Oracle DB and IBM DB2. We do know that there is a "cult" of people that believe that PostgreSQL is "enterprise" and MySQL is "toy", but given that MySQL dominates the highend over PostgreSQL the reality seems to be the exact opposite. Arne
From: Arne Vajhøj on 22 Nov 2009 22:18 Lew wrote: > <http://troels.arvin.dk/db/rdbms/> > has a fairly comprehensive comparison of various RDBMSes, but also fails > to mention Derby and HSQL. He compares all the big ones. Derby and HSQL are not widely used in production and in reality Java only. Arne
From: Lew on 23 Nov 2009 00:38
Arne Vajhøj wrote: >> http://www.postgresql.org/docs/8.2/interactive/triggers.html For reference, Postgres 8.2 is an old version. The current version is 8.4. Naturally that does not change your main point. As for PG PL/pgSQL's similarity to Oracle PL/SQL, there is a chapter: <http://www.postgresql.org/docs/8.4/interactive/plpgsql-porting.html> that discusses that. -- Lew |