On platforms with sizeof(int) == sizeof(apr_size_t), the change is a noop, so no break there.
On other platforms, any indirect lock records which have already been written to the database by the <=2.0.50 code will be corrupt and unreadable anyway. If no indirect records have been written it doesn't matter, and any new records which are written by the new code will be OK.
Hope that makes sense...
Yup. Thanks! -- justin
