SELECT data_key, data_value
FROM xf_data_registry
WHERE data_key IN ('options', 'languages', 'contentTypes', 'codeEventListeners', 'deferredRun', 'simpleCache', 'addOns', 'defaultStyleProperties', 'routeFiltersIn', 'routeFiltersOut', 'routesPublic', 'nodeTypes', 'bannedIps', 'discouragedIps', 'styles', 'displayStyles', 'userBanners', 'smilies', 'bbCode', 'threadPrefixes', 'userTitleLadder', 'reportCounts', 'moderationCounts', 'userModerationCounts', 'notices', 'userFieldsInfo')
Run Time: 0.000621
Select Type | Table | Type | Possible Keys | Key | Key Len | Ref | Rows | Extra |
---|
SIMPLE | xf_data_registry | range | PRIMARY | PRIMARY | 27 | | 26 | Using where |
SELECT data_key, data_value
FROM xf_data_registry
WHERE data_key IN ('brListenerClasses', 'brBriviumAddOns')
Run Time: 0.000152
Select Type | Table | Type | Possible Keys | Key | Key Len | Ref | Rows | Extra |
---|
SIMPLE | xf_data_registry | range | PRIMARY | PRIMARY | 27 | | 2 | Using where |
SELECT *
FROM xf_brivium_addon
ORDER BY addon_id
Run Time: 0.000145
Select Type | Table | Type | Possible Keys | Key | Key Len | Ref | Rows | Extra |
---|
SIMPLE | xf_brivium_addon | index | | PRIMARY | 77 | | 1 | |
INSERT INTO xf_data_registry
(data_key, data_value)
VALUES
(?, ?)
ON DUPLICATE KEY UPDATE
data_value = VALUES(data_value)
Params: brBriviumAddOns, a:0:{}
Run Time: 0.000116
SELECT cache_value
FROM xf_permission_combination
WHERE permission_combination_id = ?
Params: 1
Run Time: 0.000145
Select Type | Table | Type | Possible Keys | Key | Key Len | Ref | Rows | Extra |
---|
SIMPLE | xf_permission_combination | const | PRIMARY | PRIMARY | 4 | const | 1 | |
SELECT thread.*
,
user.gender, user.avatar_date, user.gravatar,
NULL AS thread_read_date,
0 AS thread_reply_banned,
0 AS thread_is_watched,
'' AS draft_message, NULL AS draft_extra
FROM xf_thread AS thread
LEFT JOIN xf_user AS user ON
(user.user_id = thread.user_id)
WHERE thread.thread_id = ?
Params: 32832
Run Time: 0.000383
Select Type | Table | Type | Possible Keys | Key | Key Len | Ref | Rows | Extra |
---|
SIMPLE | thread | const | PRIMARY | PRIMARY | 4 | const | 1 | |
SIMPLE | user | const | PRIMARY | PRIMARY | 4 | const | 1 | |
SELECT node.*, forum.*
,
permission.cache_value AS node_permission_cache,
NULL AS forum_read_date
FROM xf_forum AS forum
INNER JOIN xf_node AS node ON (node.node_id = forum.node_id)
LEFT JOIN xf_permission_cache_content AS permission
ON (permission.permission_combination_id = 1
AND permission.content_type = 'node'
AND permission.content_id = forum.node_id)
WHERE node.node_id = ?
Params: 16
Run Time: 0.004956
Select Type | Table | Type | Possible Keys | Key | Key Len | Ref | Rows | Extra |
---|
SIMPLE | forum | const | PRIMARY | PRIMARY | 4 | const | 1 | |
SIMPLE | node | const | PRIMARY | PRIMARY | 4 | const | 1 | |
SIMPLE | permission | const | PRIMARY | PRIMARY | 35 | const,const,const | 1 | |
SELECT post.*
,
thread.*, thread.user_id AS thread_user_id, thread.username AS thread_username,
thread.post_date AS thread_post_date,
post.user_id, post.username, post.post_date,
bb_code_parse_cache.parse_tree AS message_parsed, bb_code_parse_cache.cache_version AS message_cache_version,
user.*, IF(user.username IS NULL, post.username, user.username) AS username,
user_profile.*,
user_privacy.*,
signature_parse_cache.parse_tree AS signature_parsed, bb_code_parse_cache.cache_version AS signature_cache_version,
session_activity.view_date AS last_view_date,
0 AS like_date
FROM xf_post AS post
INNER JOIN xf_thread AS thread ON
(thread.thread_id = post.thread_id)
LEFT JOIN xf_bb_code_parse_cache AS bb_code_parse_cache ON
(bb_code_parse_cache.content_type = 'post' AND bb_code_parse_cache.content_id = post.post_id)
LEFT JOIN xf_user AS user ON
(user.user_id = post.user_id)
LEFT JOIN xf_user_profile AS user_profile ON
(user_profile.user_id = post.user_id)
LEFT JOIN xf_user_privacy AS user_privacy ON
(user_privacy.user_id = post.user_id)
LEFT JOIN xf_bb_code_parse_cache AS signature_parse_cache ON
(signature_parse_cache.content_type = 'signature' AND signature_parse_cache.content_id = post.user_id)
LEFT JOIN xf_session_activity AS session_activity ON
(post.user_id > 0 AND session_activity.user_id = post.user_id AND session_activity.unique_key = CAST(post.user_id AS BINARY))
WHERE (
(post.thread_id = ? AND (post.position >= 0 AND post.position < 10) )
)
AND (post.message_state IN ('visible'))
ORDER BY post.position ASC, post.post_date ASC
Params: 32832
Run Time: 0.010672
Select Type | Table | Type | Possible Keys | Key | Key Len | Ref | Rows | Extra |
---|
SIMPLE | thread | const | PRIMARY | PRIMARY | 4 | const | 1 | Using filesort |
SIMPLE | post | ref | thread_id_post_date,thread_id_position | thread_id_post_date | 4 | const | 1 | Using index condition; Using where |
SIMPLE | bb_code_parse_cache | eq_ref | content_type_id | content_type_id | 31 | const,xenforo.cc.post.post_id | 1 | Using where |
SIMPLE | user | eq_ref | PRIMARY | PRIMARY | 4 | xenforo.cc.post.user_id | 1 | |
SIMPLE | user_profile | eq_ref | PRIMARY | PRIMARY | 4 | xenforo.cc.post.user_id | 1 | |
SIMPLE | user_privacy | eq_ref | PRIMARY | PRIMARY | 4 | xenforo.cc.post.user_id | 1 | |
SIMPLE | signature_parse_cache | eq_ref | content_type_id | content_type_id | 31 | const,xenforo.cc.post.user_id | 1 | Using where |
SIMPLE | session_activity | eq_ref | PRIMARY | PRIMARY | 22 | xenforo.cc.post.user_id,func | 1 | Using where |
INSERT INTO xf_thread_view
(thread_id)
VALUES
(?)
Params: 32832
Run Time: 0.000087
INSERT INTO `xf_session` (`session_id`, `session_data`, `expiry_date`) VALUES (?, ?, ?)
Params: 60a27a26f3bb3f7b4f3ad77a2443c826, , 1714360967
Run Time: 0.000764
INSERT INTO xf_session_activity
(user_id, unique_key, ip, controller_name, controller_action, view_state, params, view_date, robot_key)
VALUES
(?, ?, ?, ?, ?, ?, ?, ?, ?)
ON DUPLICATE KEY UPDATE
ip = VALUES(ip),
controller_name = VALUES(controller_name),
controller_action = VALUES(controller_action),
view_state = VALUES(view_state),
params = VALUES(params),
view_date = VALUES(view_date),
robot_key = VALUES(robot_key)
Params: 0, , , XenForo_ControllerPublic_Thread, Index, valid, thread_id=32832, 1714357367,
Run Time: 0.000102
INSERT INTO xf_bb_code_parse_cache
(content_type, content_id, parse_tree, cache_version, cache_date)
VALUES (?, ?, ?, ?, ?)
ON DUPLICATE KEY UPDATE parse_tree = VALUES(parse_tree),
cache_version = VALUES(cache_version),
cache_date = VALUES(cache_date)
Params: post, 33387, a:6:{i:0;s:1046:"iPhone 5 除了使用自家地圖出事外, 近期被炒得熱烘烘的, 就是其機背攝影鏡頭 iSight, 在陽光等強光直射下出現的 「紫色光暈」 問題. 美國權威雜誌 Consumer Reports 於星期三發佈了一份報告, 針對一系列的智能手機攝影鏡頭作出測試, 當中發現 「紫色光暈」 的問題並非 iPhone 5 獨有, 而其他品牌的智能手機證實也有同樣情況出現.
Consumer Reports 指出, iPhone 5 的機背攝影鏡頭 iSight 在強光直射下確實出現 「紫色光暈」, 但亦不至於讓人大驚小怪; 乃因其他的智能手機也有這樣的問題. 在相同的拍照環境下, Consumer Reports 分別以 Apple iPhone 4S, Apple iPhone 5, SamSung Galaxy SIII, 及 Motorola Droid Razr Maxx 的攝影鏡頭作出測試. 測試結果發現, 在相同的拍照環境 (強光) 下, 大部分手機均產生了不同顏色, 及不同程度的光暈問題. 經智能手機拍攝時出現的光暈, 有時候會呈現紫色, 但在部份實驗中則出現過彩虹色的結果.
";i:1;a:4:{s:3:"tag";s:3:"url";s:6:"option";s:89:"http://www.news.gizzomo.com/wp-content/uploads/2012/10/gizzomo-iphone-5-purple-haze-1.jpg";s:8:"original";a:2:{i:0;s:97:"[URL='http://www.news.gizzomo.com/wp-content/uploads/2012/10/gizzomo-iphone-5-purple-haze-1.jpg']";i:1;s:6:"[/URL]";}s:8:"children";a:1:{i:0;a:4:{s:3:"tag";s:3:"img";s:6:"option";N;s:8:"original";a:2:{i:0;s:5:"[IMG]";i:1;s:6:"[/IMG]";}s:8:"children";a:1:{i:0;s:89:"http://www.news.gizzomo.com/wp-content/uploads/2012/10/gizzomo-iphone-5-purple-haze-1.jpg";}}}}i:2;s:515:"
Consumer Reports 進一步指出, 其實所有相機拍攝時均會有光暈現象, 即使是專業單反(SLR) 鏡頭也不例外. 只要攝影鏡頭接觸明亮的光源時, 就會產生光線折射; 而光暈的嚴重程度, 就取決於鏡頭暴露於強光的範圍. 研究人員稱這種問題「可能相當惱人」, 同時亦表示在大多數的拍照的情況下不至於有太大影響. Consumer Reports 建議用家在陽光下拍照時, 可以用手遮擋陽光, 將光暈現象範圍減至到最小.
";i:3;a:4:{s:3:"tag";s:3:"url";s:6:"option";s:89:"http://www.news.gizzomo.com/wp-content/uploads/2012/10/gizzomo-iphone-5-purple-haze-2.jpg";s:8:"original";a:2:{i:0;s:97:"[URL='http://www.news.gizzomo.com/wp-content/uploads/2012/10/gizzomo-iphone-5-purple-haze-2.jpg']";i:1;s:6:"[/URL]";}s:8:"children";a:1:{i:0;a:4:{s:3:"tag";s:3:"img";s:6:"option";N;s:8:"original";a:2:{i:0;s:5:"[IMG]";i:1;s:6:"[/IMG]";}s:8:"children";a:1:{i:0;s:89:"http://www.news.gizzomo.com/wp-content/uploads/2012/10/gizzomo-iphone-5-purple-haze-2.jpg";}}}}i:4;s:274:"
iPhone 5 推出數天, 紫色光暈的問題便在網絡上炒得火熱, 更一度有人推測為 iPhone 本身的缺陷. 經深入調查後證實, 類似問題乃出現在許多數碼相機中, 尤其是小型行動設備所附的鏡頭; 用家無須太驚小怪.
Source: ";i:5;a:4:{s:3:"tag";s:3:"url";s:6:"option";s:125:"http://news.consumerreports.org/electronics/2012/10/our-tests-find-purple-haze-problem-isnt-limited-just-to-the-iphone-5.html";s:8:"original";a:2:{i:0;s:133:"[URL='http://news.consumerreports.org/electronics/2012/10/our-tests-find-purple-haze-problem-isnt-limited-just-to-the-iphone-5.html']";i:1;s:6:"[/URL]";}s:8:"children";a:1:{i:0;s:16:"Consumer Reports";}}}, 1621686945, 1714357367
Run Time: 0.001029