"D. Richard Hipp" <[EMAIL PROTECTED]> writes: > While on the airplane, I was able to reproduce the problem > and confirm that it is possible to corrupt a database > as described above. I've just checked in a tentative fix. > After some more testing, I will do a new release, probably > 3.1.2 (stable).
Do you know if this bug exist in 2.8.15 as well? If so, is the fix back-portable? Thanks, Derrell
