Re: transactions from PHP - double COMMIT required?
От | mikie |
---|---|
Тема | Re: transactions from PHP - double COMMIT required? |
Дата | |
Msg-id | ca35ce500703010445n67ca6714id0b10b393859f8e0@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: transactions from PHP - double COMMIT required? ("David Legault" <legault.david@gmail.com>) |
Ответы |
Re: transactions from PHP - double COMMIT required?
Re: transactions from PHP - double COMMIT required? |
Список | pgsql-php |
2007/3/1, David Legault <legault.david@gmail.com>: > If you are using PHP5 (and the PDO PGSQL) I would suggest you use exceptions to trap the error > > try { > > $db->beginTransaction(); > > // other queries here, if one fails, an exception is thrown > > $db->commit(); > } > catch (Exception $e) { > > // do whatever with error > $db->rollback(); > > } Yes, that is nice way to work with databases, but I am on PHP4 and I am not using the PDO. But getting back to my problem - perhaps there is something I misunderstood: is it the client application responsibility to check if the transaction failed or succeeded and issue COMMIT or ROLLBACK accordingly (how do I close the transaction block in that case)? Or is it the database server that is suppose to check if transaction succeded and perform the query, or ROLLBACK if anything went wrong? -- Mike
В списке pgsql-php по дате отправления: