[...] > My questions to the sybase_ct (Hi Timm ;-) ) maintainer: > > 1. How is the deadlock/retry logic in sybase_ct_query() > intended to work? From my understanding a single SQL > statement will never deadlock.
I have no idea why this was put in in the first place. > 2. The default setting of deadlock_retry_count = -1 leads to > uncontrolled behaviour, if external transactions deadlock and > are rolled back by the server. In this case a clean exit is > much better than retrying the LAST statement of the aborted > transaction. My suggestion therefore is changing the default > to deadlock_retry_count=0. I have nothing against that. I set it to -1 to ensure backwards compatibility. If no one objects, I'll commit that to CVS head. - Timm -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
