From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
---|---|
To: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>, pgsql-advocacy(at)postgresql(dot)org |
Subject: | Re: [jforman@tecso.com.br: RES: Database comparison question] |
Date: | 2004-04-27 16:01:14 |
Message-ID: | 200404271201.14195.xzilla@users.sourceforge.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
Karen,
I've written up some brief answers regarding the list availabel at
http://www.danlj.org/~danlj/OpenSource/Database_Comparisons.doc.html
perhaps you could forward it on?
PostgreSQL
Price: Free for commercial or non-commercial use. Extended versions are
available from several vendors as commercial offerings as well.
Relational Database: Yes
Support Views: Yes. Updatable view support is available using the PostgreSQL
Rules system.
Stored Procedures: Yes. We have an oracle like implementation in plpgsql and
also have implementations in more than half a dozen additional languages such
as plperl,plpython,pltcl,plphp,pljava, and plr
Foreign Keys: Yes
Job Schedular: No. (Due to our mostly *nix oriented install base, we
generally recommend using cron)
Multiple CPU support for Insert/Select,Update,Delete,Index: No (assuming this
is reffering to multiple CPU used on one query. We certainly support
multiple CPU's otherwise)
Send messages to DBA based on Alerts: No. (Similar to cron this is unix
functionality that we currently do not duplicate)
Data Transformations Services: Yes.
Transaction Support: Yes.
Referential Integrity: Yes.
Clustering: Commercial solutions are available from 3rd party vendors.
Robert Treat
On Wednesday 21 April 2004 04:52, Karsten Hilbert wrote:
> Dear advocacy team,
>
> attached find a posting from the openhealth list. The story
> behind this is that a colleague of one of the posters there
> (Dan Johnson at Mayo Clinics) asked the OP to help him divert
> the flak he was getting at his hospital IT dept. for
> proffering OS solutions. The "bad guys" compared MS SQL and
> MySQL concluding the latter and thusly all OS DBs are crap
> (find details in the openhealth archives).
>
> In the course of discussion someone posted the attached
> comparison between PG and MySQL (note, it is not the poster's
> work). There are gaping errors in there that I wanted to bring
> to your attention.
>
> Now, the people on openhealth are typically very clever and
> well-mannered if that has any influence on how you might react
> to the attached posting should you choose to do so.
>
> I already posted the URL to your site and the URL to the MySQL
> Gotcha's site.
>
> Oh, me personally, I hear you say ? Well, I am just a humble
> developer with GnuMed (http://www.gnumed.org) -- based on
> PostgreSQL, of course :-)
>
> Karsten Hilbert, MD
> GnuMed i18n coordinator
> Leipzig, Germany
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | Tim Conrad | 2004-04-27 16:07:11 | Re: [HACKERS] What can we learn from MySQL? |
Previous Message | Marc G. Fournier | 2004-04-27 15:58:59 | Re: [HACKERS] What can we learn from MySQL? |