Fill write_uid on record creation

[Grzegorz Grzelak (OpenGLOBE.pl)]

Please can you point out on the problem of Python developers:
If they want to show on form or tree view who was the last editor of the record they have to add some code and separate field into the object.

Thats because write_uid field is empty when record is created. And developer have to write code checking if write_uid is empty, and according to that take write_uid or create_uid. Additionally he has to add additional field to the object to show last editor properly.

It would simplify the developing a lot if write_uid is filled on record creation. In such case developer can only add write_uid to view. I think it is very easy change and I don't believe it make trouble in any convention. You always know who is creator anyway. Only code checking if record was changed since creation has to be changed from simple checking if write_uid is empty to comparing write_uid with create_uid. Do we have a lot of such code?

Please change the code to have write_uid always filled. I am sure we gain more than loose.

I have written a blueprint for that too:
https://blueprints.launchpad.net/openobject-server/+spec/write-uid-equal-create-uid-on-creation

And another suggestion is to add server (base) UI functionality to make possible to check: create_uid, create_date, write_uid, write_date after right click on record or on icon placed on every view.

[Fabien (Open ERP) (fp-tinyerp)]

fill in write_uid and write_date at record creation.