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

From: merlyn(at)stonehenge(dot)com (Randal L(dot) Schwartz)
To: "Jay O'Connor" <joconnor(at)cybermesa(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL
Date: 2003-12-02 02:29:18
Message-ID: 86fzg47y0x.fsf@blue.stonehenge.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>>>>> "Jay" == Jay O'Connor <joconnor(at)cybermesa(dot)com> writes:

Jay> Python also reads more obviously, in that it doesn't have a lot of
Jay> 'default context' ($_) and 'scalar context versus array context' and
Jay> cute shortcuts and stuff floating around, which makes it easier to
Jay> read, and more importantly easier for teams to read.

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.

--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn(at)stonehenge(dot)com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jonathan Bartlett 2003-12-02 02:44:14 Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL
Previous Message Alvaro Herrera 2003-12-02 01:17:34 Re: PG_DUMP question