Closed (fixed)
Project:
Drupal core
Version:
7.x-dev
Component:
database system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
29 Mar 2010 at 03:35 UTC
Updated:
19 Aug 2010 at 21:40 UTC
Jump to comment: Most recent file
Comments
Comment #2
jbrown commentedAhh, empty fields in the object need to be populated with default values for the caller.
Comment #3
jbrown commentedWhy is it ignored?
Comment #4
jbrown commentedAttempting with different filename.
Comment #5
berdirBecause the issue is set to needs work :)
Comment #6
Crell commentedI think this makes, sense, if I understand it all correctly. :-)
Comment #7
jbrown commentedUpdated a comment.
Benefits of this patch:
Comment #8
jbrown commentedUpdated patch.
Now $record will not be converted to an object if an exception occurs - #731554: drupal_write_record() silently converts an array to an object in case of an exception
Comment #9
jbrown commentedwith new casting coding standards...
Comment #10
Crell commentedI'm OK with this assuming the bot is. If that fixes the other issue as well, score.
Comment #11
rfayOK, seems like Crell and the bot are good with it. Who could ask for more?
Looks OK to me. I tested and it resolves #731554: drupal_write_record() silently converts an array to an object in case of an exception and I do like this approach better.
Comment #12
aspilicious commented#9: dont-insert-default-values.patch queued for re-testing.
Comment #13
aspilicious commented*Retesting old patches*
Comment #14
jbrown commented#9: dont-insert-default-values.patch queued for re-testing.
Comment #15
jbrown commentedCan this be committed?
Comment #16
webchickThis looks like a nice clean-up. I hope our test coverage here is good...
Committed to HEAD.
Comment #17
jbrown commentedGreat! This one is also ready: #797680: drupal_write_record() unnecessarily sets primary keys while updating