This is a model issue, so there's nothing that can be done about it without destroying performance through extra API calls that check for and correct it.
