From: | "Adam Lang" <aalang(at)rutgersinsurance(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Re: php as stored procedures |
Date: | 2001-01-31 18:36:53 |
Message-ID: | 00c101c08bb4$c8510160$330a0a0a@rutgersinsurance.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Stored procedures put LESS strain on a database.
When you send a query to postgres via PHP, postgres runs the query.
If you have a stored procedure on postgres and have PHP use that to execute
the query, you get better performance since stored procedures are (should
be) precompiled.
In both situations the db server does the work.
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "Mike Sears" <matrix(at)quadrent(dot)net>
To: <pgsql-general(at)postgresql(dot)org>; "Doug McNaught" <doug(at)wireboard(dot)com>
Sent: Wednesday, January 31, 2001 12:43 PM
Subject: [GENERAL] Re: php as stored procedures
> what would the over all benifit be to using stored procedures instead of
> just going about php normaly?
>
> would that not put a bit of stress on the db server as well?
>
> Mike
From | Date | Subject | |
---|---|---|---|
Next Message | Keith Perry | 2001-01-31 18:43:10 | How do I list all tables? |
Previous Message | Barnes, Sandy (Sandra) | 2001-01-31 18:28:01 | [HACKERS] ERROR: "Database 'products', OID nnn, has disappeared from pg_database" |