[PHP-DB] Re: Database Transactions and HTTP statelessness

2001-08-31 Thread John Lim
There is no need to use transactions if you are dealing with 1 table. Have a version column in the table which is numeric. When you first select/edit the record, store the version number. When you update, use: update table set version = version + 1, data = ... where key=$id and version =

[PHP-DB] Re: Database Transactions and HTTP statelessness

2001-08-29 Thread Bopolissimus Platypus
On Tue, 28 Aug 2001 23:55:32 -0300, [EMAIL PROTECTED] (Manuel Lemos) wrote: The solution is to pass data between pages and only commit it when you are done with all the data that you need to grab from the user. Transactions can't be kept between HTTP requests, but you can pass data between pages

RE: [PHP-DB] Re: Database Transactions and HTTP statelessness

2001-08-29 Thread Dave Watkinson
[mailto:[EMAIL PROTECTED]] Sent: 29 August 2001 13:10 To: [EMAIL PROTECTED] Subject: [PHP-DB] Re: Database Transactions and HTTP statelessness On Tue, 28 Aug 2001 23:55:32 -0300, [EMAIL PROTECTED] (Manuel Lemos) wrote: The solution is to pass data between pages and only commit it when you are done

[PHP-DB] Re: Database Transactions and HTTP statelessness

2001-08-28 Thread Manuel Lemos
Hello, Bopolissimus Platypus wrote: hello all, I've got a question about what's got to be a common problem. I'm sort of doing a survey to see how others have solved this problem before so that I can choose one that's best for me. Basics: The software is a web based data entry