Re[2]: [PEAR-DEV] mysql and transactions
| From: | Oleg Rekutin | Date: | Fri, 27 Jul 2001 03:03:45 +0000 |
| Subject: | Re[2]: [PEAR-DEV] mysql and transactions | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-1085@lists.php.net to get a copy of this message | ||
On Thursday, July 26, 2001, 10:50:28 PM, in message "[PEAR-DEV] mysql
and transactions", Tomas wrote:
TVVC> Oleg Rekutin wrote:
>>
TVVC> Yes this is the idea :) I think that: if native mysql doesn't support
TVVC> transactions, we don't want to give methods to developers that won't
TVVC> work as expected (as you told with the rollback problem) and it's
TVVC> probably difficult (imposible?) to check if the table supports or not
TVVC> transactions, the only solution I saw was to change this flag. If your
TVVC> MySQL do support transactions: why not change the flag?
TVVC> Any way was only an idea.
Actually, it's possible to detect whether a particular table supports
transactions by querying its type. At the moment of writing, only
"BDB", "InnoDB", and "GEMINI" types (last one is currently not in the
MySQL distro) support transactions. Of course, transactions often
enough involve more than one table and one of them may not support
transactions.
It's conceptually wrong to tell the database what its capabilities
are. It's supposed to be vice versa.
Hmm, don't know how this should be handled...
- Oleg