Hi Listmembers, I found a detail in the documentation that is described ambiguous. I normaly use the german localized compiled help-file, but the same information can be found in the english documentation too, so I will describe the point referring on the english manual:
Opening the description of 'Locks' in the helpfile, there is a table 'Releasing Locks'. Under this table you can find the following information: "Use the REQUEST_TIMEOUT special database parameter to restrict the time that users wait for a lock to be released. When this time runs out, there is a database system message and you can react to it by terminating the transaction, for example. In such situations, the database system does not perform an implicit ROLLBACK." Having a closer look on the special DB-parameter REQUEST_TIMEOUT in the reference, you can find the following information: "Maximum wait time for a lock to be released (in s); for all database sessions, restricts waiting for a lock to be released by another user. If a lock request cannot be fulfilled in the time defined here, a message is sent to the waiting database session. The changes that may have been made within the transaction earlier are rolled back." So the documentation states that no implicit rollback will occur as a result of a timout in the first quoted part, while in the second part it is said that an implicit rollback will happen in such situations. I tried it by myself and found, that the second information is right: A timeout causes a rollback. It would be nice to see the manual updated in this detail ;) Thanks & regards -- Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko! Satte Provisionen für GMX Partner: http://www.gmx.net/de/go/partner -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
