3.2.x is really, really out-dated and no longer maintained. If this is still an issue on ORM 4, attach a test case?