Re: DB transaction support
| From: | Filippo Veneri | Date: | Wed, 22 Jan 2003 09:39:08 +0000 |
| Subject: | Re: DB transaction support | ||
| References: | 1 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-3397@lists.php.net to get a copy of this message | ||
On Wed, 2003-01-22 at 05:27, Fredrik Svensson wrote:
> Hi,
>
> I was just wondering a little about the transaction support in PEAR >
> DB. Why
> is it designed to start the transaction at the first query after a
call to
> autoCommit(false) and not something like begin()? In oracle for
> instance if
> I remember correctly you can have nested named transactions. With the
> pear
> approach you seem to be left with only one transaction that pear
controls
> for you for all querys...
> I would have though a syntax like begin(transactionName) would have
been a
> possibility but maybe I'm just lost somewhere in outer space.
I agree with you. The explicit approach using begin() semms to me more
natural than the somewhat implicit autoCommit(false) procedure, even for
backends that don't support nested named transactions.
But maybe i am missign something too.
bye,
fbv