Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL Advocacy, Thoughts and Comments - Mailing list pgsql-general

From Paul Thomas
Subject Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL Advocacy, Thoughts and Comments
Date
Msg-id 20031129143034.G9760@bacon
Whole thread Raw
In response to Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL Advocacy, Thoughts and Comments  ("Rod K" <rod@23net.net>)
Responses Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL Advocacy, Thoughts and Comments
List pgsql-general
On 29/11/2003 12:53 Rod K wrote:
> [snip]
> > You are, of course, free to do whatever want. But if you have to use
> > features of the database to compensate for inadequacies in your
> > programming language maybe you should be using another language?
>
> This doesn't even make sense in the context of Jasons remark.

It makes sense to me. Maybe English is a write-only language after-all ;-)

> [snip]
> > Much of the populatity of MySQL seems to stem from PHPs out-of-the-box
> > support for it. With the MySQL client library license change, this
> > situation will probably change. There was a long thread about
> > this earlier
> > this year. Check the archives.
> >
> >
> This is incorrect.  The embedded mysql client library was not added until
> PHP4.0 RC1.

Thats not the impression I got from from reading the thread concening
MySQL/PHP et al earlier this year. But whatever the exact historical
details are, the current popularity of MySQL as the back-end for PHP apps
is well-documented.

> PHP's popularity existed long before this.  The real culprit
> causing the popularity of MySQL was it's ubiquity among hosting providers
> and the virtual non-existence of PG in that arena.  If PG had been more
> friendly to shared hosting environments, perhaps this situation wouldn't
> have arisen.

I think culprit is a bit strong. If I were in the hosting business a few
years ago I would probably have made the same decision on the belief that
most people would not need anything more than a few rudimentary database
features for which MySQL would suffice.
> Blaming PHP for this situation (and your other comments) show
> extreme prejudice.

Where have I blamed PHP for anything? Nowhere. As for extreme predudice,
if you wish to grosely mis-interpret my opinions of the limitations of cgi
scripts in that way, thats fine by me.

--
Paul Thomas
+------------------------------+---------------------------------------------+
| Thomas Micro Systems Limited | Software Solutions for the Smaller
Business |
| Computer Consultants         |
http://www.thomas-micro-systems-ltd.co.uk   |
+------------------------------+---------------------------------------------+

pgsql-general by date:

Previous
From: "Jay O'Connor"
Date:
Subject: Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL
Next
From: "Rod K"
Date:
Subject: Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL Advocacy, Thoughts and Comments