Received: from postgresql.org.org (webmail.postgresql.org [216.126.85.28]) by postgresql.org (8.11.3/8.11.1) with SMTP id f4BDlGA76233 for ; Fri, 11 May 2001 09:47:16 -0400 (EDT) (envelope-from pgsql-php-owner@postgresql.org) Received: from viemta04.chello.at (viemta04.chello.at [195.34.133.54]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f4A0IvA86981 for ; Wed, 9 May 2001 20:18:57 -0400 (EDT) (envelope-from cm@chello.at) Received: from server ([212.17.110.55]) by viemta04.chello.at (InterMail vK.4.03.02.00 201-232-124 license 6aea1bd1f01aef5a9a73363c16ebee43) with ESMTP id <20010510001853.IRZU2375.viemta04@server> for ; Thu, 10 May 2001 02:18:53 +0200 From: "Christian Marschalek" To: "[PHP] PostgreSQL" Subject: User reloads inert script... Date: Thu, 10 May 2001 02:20:14 +0200 Message-ID: <000401c0d8e6$fe3d93e0$0200a8c0@server> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Archive-Number: 200105/65 X-Sequence-Number: 374 Hey there:) What would you do? Situation: you have a script doing some HTML formular data processing, some selects and inserts in a transaction and some html output. When the script is cancled on the client side. By normal PHP will cancel the script it self (which can be prevented). Now hopefully the transaction will be rolled back on PostgreSQLs side. Everything fine... But what If the user reloads the page? Then the whole process will be done twice... How would you prevent that? Tia! Chris