Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL - Mailing list pgsql-general

From merlyn@stonehenge.com (Randal L. Schwartz)
Subject Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL
Date
Msg-id 86fzg47y0x.fsf@blue.stonehenge.com
Whole thread Raw
In response to Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL  ("Jay O'Connor" <joconnor@cybermesa.com>)
Responses Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-general
>>>>> "Jay" == Jay O'Connor <joconnor@cybermesa.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@stonehenge.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!

pgsql-general by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: PG_DUMP question
Next
From: Jonathan Bartlett
Date:
Subject: Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL