| From: | Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: more anti-postgresql FUD |
| Date: | 2006-10-16 09:45:40 |
| Message-ID: | 20061016114540.4a1256cc@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Mon, 16 Oct 2006 11:05:33 +0200
Alban Hertroys <alban(at)magproductions(dot)nl> wrote:
> This does require some way for the client to keep a single
> transaction open. If this kind of query is performed by a web
> application (as is often the case), the "client" is the server side
> web script engine, and not all of those beasts are capable of
> keeping a transaction open across pages (PHP comes to mind).
> This combined with expensive (complex) queries is regularly a pain.
But which scripting language in a web environment (read running under Apache) is able to keep transactions open across pages?
--
Ivan Sergio Borgonovo
http://www.webthatworks.it
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gandalf | 2006-10-16 10:59:44 | Fast backup/restore |
| Previous Message | Ivan Sergio Borgonovo | 2006-10-16 09:41:25 | Re: exploiting features of pg to obtain polymorphism |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mark | 2006-10-16 10:40:10 | Re: Postgresql Caching |
| Previous Message | Alban Hertroys | 2006-10-16 09:05:33 | Re: more anti-postgresql FUD |