Re: [0.0] Re: [0.2] getting transactions to work - Mailing list pgsql-php

From reiner peterke
Subject Re: [0.0] Re: [0.2] getting transactions to work
Date
Msg-id 2809A35D-E2D2-11D8-ACD4-000A95984CA6@drizzle.com
Whole thread Raw
In response to Re: [0.0] Re: [0.2] getting transactions to work  (Thom Dyson <TDyson@sybex.com>)
List pgsql-php
thanks for all the feed back
at least now i have a better idea on how to proceede.

r
On 30 jul 2004, at 20.48, Thom Dyson wrote:

>
>
>
>
> 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@postgresql.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
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to
> majordomo@postgresql.org
>


pgsql-php by date:

Previous
From: Frank Finner
Date:
Subject: Re: [0.2] getting transactions to work
Next
From: Lynna Landstreet
Date:
Subject: Re: Strange warning message