I believe that you should use User.create instead of update_fields=['id'], e.g.:

user.id = 123
new_user = await user.create(**dict(user))

That would work in most cases, but the idea is to be able to change the ID while preserving all the other data, not to delete and re-create. The SQL would look like this: UPDATE users SET id=123 WHERE id=100.

I suppose this could break foreign-key references to the updated object. Also I'm not needing to do this in my code after all, so it's not high priority. At least we should get a nicer error message, which I see @waketzheng is doing.

That would work in most cases, but the idea is to be able to change the ID while preserving all the other data, not to delete and re-create. The SQL would look like this: UPDATE users SET id=123 WHERE id=100.

i don't think it is valid to update primary keys. For instance, when changing the id of an object, Django creates a copy of the object with the new id. However, I think it's better to raise an error in this case and force the user to actually create a new object if they want to have a duplicate. It is less error prone and seems more correct.

Makes sense to me.