Hi, > Do you have any ideas how to handle this case at the core level in the > regard of php lifecycle?
I agree with Kentaro on this. This can be said to be a weakness of two-phase commit itself, but I think it should be addressed in userland or user operations. BTW, I said that I was thinking of implementing two-phase commit in pdo core, but that may be a bit unreasonable. Perhaps because it is not standardized in standard SQL, the method of implementing this function varies from database to database. The steps leading up to the final commit vary greatly depending on the DB. Looking at the current implementation for each DB, it is possible to forcefully create a method in the core, but this will break down when the DB specifications change in the future. Perhaps two-phase commit is a feature that should be implemented in pdo subclasses with "retaining the personality of the DB''. Regards. Saki -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
