Thanks for pointing this out. I've pulled up the fix for it to our stable branch, and it will appear in the next 1.2.9 release candidate. Garry