Closed (fixed)
Project:
Drupal core
Version:
7.x-dev
Component:
base system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
1 Jul 2008 at 22:18 UTC
Updated:
23 Jul 2008 at 10:56 UTC
Jump to comment: Most recent
Comments
Comment #1
damien tournoud commentedWell. PHP is a loosely typed language, after all, so I can't see how this could be a problem. At least, that's not critical.
However, the patch looks good and promote consistency, so marking as RTBC.
Comment #2
dries commentedPlease write some tests for this. It is important when people write an alternative cache backend. They could re-use these tests. Thanks!
Comment #3
R.Muilwijk commented@Dries, as said in the topic the tests are already written on: http://drupal.org/node/276267
Comment #4
dries commentedCommitted to CVS HEAD. Good catch.
Comment #5
Anonymous (not verified) commentedIs it possible that cache_set could be storing a resource id? If so then we need to also filter !is_resource($data) because you cannot serialize a resource. Actually, I'm not sure we shouldn't also serialize the strings. So I think we should instead do
Comment #6
cwgordon7 commentedLet the resources get serialized.
Comment #7
Anonymous (not verified) commentedFrom http://us2.php.net/manual/en/function.serialize.php we see
Comment #8
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.