2011-03-14 09:27:40 PDT
Hi Lem9,
Below is an example. The problem is that Drupal7 stores serialized php data into blob fields.
Developers and admins will want to "see" whats in those fields for debugging. Having this available in the "browse table" view saves a click, and gives awareness of the unexpected when browsing: "Wait, why is it set to *that*?"
By default on Ubuntu, the blobs are all locked up. With the config changes above, the data is available on the row detail page. Here is an example of making it available on the "browse table" page:
Current browse table list on "cache_update" table:
Edit Delete fetch_task::drupal [BLOB - 0B] 0 1295545751 0
Edit Delete update_project_projects [BLOB - 1.2KiB] 1295549351 1295545751 1
...
Blob summary table list: (note the blob data is truncated for first 10 or so characters)
Edit Delete fetch_task::drupal [BLOB - 0B] 0 1295545751 0
Edit Delete update_project_projects a:1:{s:6:"drup 1295549351 1295545751 1
...
Current browse table list on "variable" table - used to store random config variables:
Edit Delete admin_theme [BLOB - 12B]
Edit Delete clean_url [BLOB - 8B]
Edit Delete comment_page [BLOB - 4B]
Edit Delete cron_key [BLOB - 51B]
Edit Delete cron_last [BLOB - 13B]
Edit Delete css_js_query_string [BLOB - 13B]
Edit Delete date_default_timezone [BLOB - 23B]
Edit Delete file_temporary_path [BLOB - 11B]
Edit Delete filter_fallback_format [BLOB - 18B]
...
Blob summary table list:
Edit Delete admin_theme s:5:"seven";
Edit Delete clean_url s:1:"1";
Edit Delete comment_page i:0;
Edit Delete cron_key s:43:"WfNgFkDq0vrfu1OssF9xKHyGCx5KpyS3btUiZa70eAU";
Edit Delete cron_last i:1295545751;
Edit Delete css_js_query_string s:6:"lfc1hz";
Edit Delete date_default_timezone s:15:"America/Chicago";
Edit Delete file_temporary_path s:4:"/tmp";
Edit Delete filter_fallback_format s:10:"plain_text";
...
I hope the formatting comes out ok. Thanks for taking a look.
What do you think?