Treat undef like blessed objects for the purpose of looking for special handling #106
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Suppose
foois an inflated timestamp column and$row->foois set to a true DateTime (representing a date, say, 2016-06-23T16:42:34). In the present code, these two code snippets:would do different things. The first prints
the second prints
Because
updateusesset_inflated_columns, the same behavior is visible there.This change makes
set_inflated_columnscallset_inflated_columnwhen the column is inflated and new value isundef(whichset_inflated_columnhandles correctly), which causes the two functions to behave identically in this case, which seems like the correct behavior.