Improve DataObject::set_param() handling of integer values

Registered by Tilman Blumenbach on 2010-02-17

DataObject::set_param() does not work properly if you try to set a param with an integer value which originally was set from the DB.
The problem is that all values that come from the DB are strings and that DataObject::set_param() uses the === operator to check whether it needs to mark a param as updated (e. g. if the current value and the value to set differ). Now, if one passes an integer value to this method and the param was set to the string value of that integer (e. g. from the DB), it thinks the value changed and causes unnecessary SQL queries.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Medium
Drafter:
None
Direction:
Approved
Assignee:
Tilman Blumenbach
Definition:
Approved
Series goal:
Accepted for trunk
Implementation:
Implemented
Milestone target:
milestone icon 0.0.0
Started by
Tilman Blumenbach on 2010-02-17
Completed by
Yabs on 2010-02-18

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.