Comment # 5 on bug 1208963 from 
Snapshot 0311 will contain a transactional-update fix taking care of this
transparently

You are receiving this mail because: