I'm no longer working in the somewhat bizarre environment where I originally reported this bug and am consequently not in a position to test against that database with current ORM releases.

You may as well just close this bug.