Skip site navigation (1) Skip section navigation (2)

Re: [0.0] Re: [0.2] getting transactions to work

From: Thom Dyson <TDyson(at)sybex(dot)com>
To: pgsql-php(at)postgresql(dot)org
Subject: Re: [0.0] Re: [0.2] getting transactions to work
Date: 2004-07-30 18:48:40
Message-ID: OF3F2C37EE.BD55BFDC-ON88256EE1.0066BBB1-88256EE1.00675527@sybex.com (view raw or flat)
Thread:
Lists: pgsql-php



Under PHP (or any cgi type of process), postgres sessions cannot cross
multiple html pages.  This is neither a flaw in PHP nor postgres; it is a
fact that is database and language independent.

Each page submission, that is each php invocation, starts a session that is
closed when the php script is done. the stateless nature of HTTP is at the
heart of this.  A web server sees each page request as a stand alone event,
with no relationship to any other request.  The ability to do "sessions" is
the work around to this.

So, if you need to carry information from one web page to another , you
either have to write hidden values to the html page (a bad idea on sorts of
levels) or use session variables to that PHP/postgres can retain
information.

Thom Dyson
Director of Information Services
Sybex, Inc.



pgsql-php-owner(at)postgresql(dot)org wrote on 07/30/2004 09:57:53 AM:

> i never said oracle did do that.
> i don 't have so much experience working with databases and web pages
> i do not have any understanding or misunderstanding.  i am trying to
> learn how it does work here.  to my mind it should be able to work
> within a web page.  maybe you could be so kind as to explain to me why
> it does not work.

> r


In response to

Responses

pgsql-php by date

Next:From: Frank FinnerDate: 2004-07-30 19:54:36
Subject: Re: [0.2] getting transactions to work
Previous:From: reiner peterkeDate: 2004-07-30 16:57:53
Subject: Re: [0.0] Re: [0.2] getting transactions to work

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group