Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: "Randal L(dot) Schwartz" <merlyn(at)stonehenge(dot)com>
Cc: "Jay O'Connor" <joconnor(at)cybermesa(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL
Date: 2003-12-02 04:56:55
Message-ID: 3FCC1B97.4080703@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


>It also has some things which are functions, and others which are
>methods, with no rhyme or reason except for a historical basis. And
>that's just the beginning. (Why are tuples read only? Sorry, cheap
>shot.)
>
>Please don't paint Python as nice and regular. It has nearly as many
>odd things to know as Perl does.
>
>
>
I think the last thing we need is a language war. Every language has its
cruft and problems. Use
the language that suits you best. Perl, Python, PHP are all good
languages in their own right.
Currently Python has the best server side (pl) support for PostgreSQL of
the three but that
will change after the new year.

Sincerely,

Joshua D. Drake

--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-222-2783 - jd(at)commandprompt(dot)com - http://www.commandprompt.com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Mike Mascari 2003-12-02 05:55:41 Re: Humor me: Postgresql vs. MySql (esp. licensing)
Previous Message Uwe C. Schroeder 2003-12-02 04:49:01 Re: Humor me: Postgresql vs. MySql (esp. licensing)