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.000490
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.000202
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.000362
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.000123
SELECT cache_value
FROM xf_permission_combination
WHERE permission_combination_id = ?
Params: 1
Run Time: 0.000173
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: 216760
Run Time: 0.000645
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: 25
Run Time: 0.000377
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: 216760
Run Time: 0.012749
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: 216760
Run Time: 0.000321
INSERT INTO `xf_session` (`session_id`, `session_data`, `expiry_date`) VALUES (?, ?, ?)
Params: 7d2242d5b18bb3208dad164cc0ef2d3b, , 1714747286
Run Time: 0.003977
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=216760, 1714743686,
Run Time: 0.000106
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, 222205, a:22:{i:0;s:409:"在未来的一段时间里全球平板电脑市场将会面临更加艰巨的挑战,众所周知iPad的销量已经持续几个季度下滑,更糟糕的是分析机构表示2016年平板 电脑的全球出货量还会进一步下降。对此,各家厂商也在开始探索自家的平板业务该何去何从,作为平板领导大军的苹果,也已经开始了对iPad产品线的重新思考。
";i:1;a:4:{s:3:"tag";s:1:"b";s:6:"option";N;s:8:"original";a:2:{i:0;s:3:"[B]";i:1;s:4:"[/B]";}s:8:"children";a:3:{i:0;s:26:"发iPad Pro “mini”,无";i:1;a:4:{s:3:"tag";s:3:"url";s:6:"option";s:56:"http://aos.prf.hn/click/camref:100lcC/creativeref:305225";s:8:"original";a:2:{i:0;s:64:"[URL='http://aos.prf.hn/click/camref:100lcC/creativeref:305225']";i:1;s:6:"[/URL]";}s:8:"children";a:1:{i:0;s:8:"iPad Air";}}i:2;s:4:"3?";}}i:2;s:71:"
传闻苹果将于 3 月召开春季发布会,除了 4 英寸的新";i:3;a:4:{s:3:"tag";s:3:"url";s:6:"option";s:56:"http://aos.prf.hn/click/camref:100lcC/creativeref:305226";s:8:"original";a:2:{i:0;s:64:"[URL='http://aos.prf.hn/click/camref:100lcC/creativeref:305226']";i:1;s:6:"[/URL]";}s:8:"children";a:1:{i:0;s:6:"iPhone";}}i:4;s:214:"之外,9.7 英寸的 iPad 也是另一个受人瞩目的新品,苹果去年推出了 12.9 英寸的 iPad Pro,为了给这款旗舰平板让路,标准尺寸(9.7 英寸)的 iPad Air 3 并没有出现。
";i:5;a:4:{s:3:"tag";s:3:"url";s:6:"option";s:65:"http://static.cnbetacdn.com/article/2016/0227/89ec6b01a1106ad.png";s:8:"original";a:2:{i:0;s:73:"[URL='http://static.cnbetacdn.com/article/2016/0227/89ec6b01a1106ad.png']";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:83:"http://static.cnbetacdn.com/thumb/article/2016/0227/89ec6b01a1106ad.png_600x600.png";}}}}i:6;s:939:"
过去几个月一直有消息指出苹果将会发布 iPad Air 3,直到昨天来自外媒 9to5Mac 的报道或许可以给我们重新思考未来 iPad 产品线的机会。该报道指出苹果有意将新一代的 9.7 英寸 iPad 纳入到 iPad Pro 的行列,也就是说苹果将会推出一款特性和功能和 12.9 英寸 iPad Pro 基本一致的 iPad Pro “mini”(小尺寸的 iPad Pro),iPad Air 3 很可能会再次延迟,甚至再也不会存在 iPad Air 这条产品线。
这款小尺寸的 iPad Pro 将会采用 A9X 芯片以及 4GB 的 RAM,并且采用和 iPad Pro 一样的屏幕技术,支持 Apple Pencil、配备 Smart Connector、Smart Keyboard,4 扬声器系统、颜色和容量版本和 12.9 英寸相同,价格接近 iPad Air。所以说这款全新的 9.7 英寸 iPad 为 iPad Pro mini 一点也不为过,3 月发布会,更可能是这款 iPad Pro 接替 iPad Air 产品线的开始。
";i:7;a:4:{s:3:"tag";s:1:"b";s:6:"option";N;s:8:"original";a:2:{i:0;s:3:"[B]";i:1;s:4:"[/B]";}s:8:"children";a:1:{i:0;s:38:"iPad mini和iPad Air更新空间有限";}}i:8;s:263:"
小尺寸的 iPad Pro 发布后,将会进一步简化 iPad 的产品线,消息称苹果目前已经放慢 iPad mini 和一代 iPad Air 机型的生产,也就是说在 9.7 英寸 iPad Pro 发布之后,iPad mini 2 和 iPad Air 1 有可能就此停产。
";i:9;a:4:{s:3:"tag";s:3:"url";s:6:"option";s:65:"http://static.cnbetacdn.com/article/2016/0227/a24282356c90211.png";s:8:"original";a:2:{i:0;s:73:"[URL='http://static.cnbetacdn.com/article/2016/0227/a24282356c90211.png']";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:83:"http://static.cnbetacdn.com/thumb/article/2016/0227/a24282356c90211.png_600x600.png";}}}}i:10;s:1205:"
iPad mini 2 和 iPad Air 1 获得了不少用户的青睐,前者在一些电商市场的价格仅为 1700 元左右,对于喜欢小尺寸平板的用户来说绝对是不能不考虑的一个高性价比选择,而后者在发布之初时就以轻薄等特性获得了极高的赞誉。不过苹果似乎认为,这两款型号是时候“退役”了。
其实仔细想想,7.9 英寸的 iPad mini 和 9.7 英寸的 iPad Air 的更新空间其实十分有限。自 iPad mini 2 添加了 Retina 显示屏后,这款小尺寸平板的更新就一直不明显,iPad mini 3 更是获得了“最无诚意升级”这样的“污名”,虽然 iPad mini 4 的整体表现获得了专业机构的肯定,但它在苹果的发布会中已经刷不到存在感。iPad mini 4 发布的时候,苹果只是几分钟带过,可见值得苹果大肆宣传的亮点已经不多。至于 iPad Air,我们可以回顾一下前面的几代产品:iPad、iPad 2、The new iPad、iPad with Retina、iPad Air、iPad Air 2。从命名我们可以看出,9.7 英寸的 iPad 设计一般维持两代产品,因此传闻中 iPad Air 3 的缺席甚至 iPad Air 产品线的消失,也就不难理解了。
";i:11;a:4:{s:3:"tag";s:1:"b";s:6:"option";N;s:8:"original";a:2:{i:0;s:3:"[B]";i:1;s:4:"[/B]";}s:8:"children";a:1:{i:0;s:33:"iPad Pro接管iPad产品线大旗";}}i:12;s:301:"
如果苹果真的推出 9.7 英寸的 iPad Pro 的话,或许我们还可以从中获取到这样一个信息:iPad Pro 将成为 iPad 产品线的支柱,接管整条 iPad 产品线。
推出小尺寸的 iPad Pro 之后,iPad Pro 就将形成 12.9 英寸和 9.7 英寸的产品组合。就像";i:13;a:4:{s:3:"tag";s:3:"url";s:6:"option";s:56:"http://aos.prf.hn/click/camref:100lcC/creativeref:305224";s:8:"original";a:2:{i:0;s:64:"[URL='http://aos.prf.hn/click/camref:100lcC/creativeref:305224']";i:1;s:6:"[/URL]";}s:8:"children";a:1:{i:0;s:7:"MacBook";}}i:14;s:292:"Pro 产品线一样,分成 13 英寸和 15 英寸两个版本,其中 15 英寸主打专业领域,而 13 英寸版本则在性能和体积方面做了妥协。12.9 英寸的 iPad Pro 继续为内容产出而生,而 9.7 英寸的 iPad Pro 则负责满足普通用户的日常需求。
";i:15;a:4:{s:3:"tag";s:3:"url";s:6:"option";s:65:"http://static.cnbetacdn.com/article/2016/0227/ecabf0ffe6b82a2.jpg";s:8:"original";a:2:{i:0;s:73:"[URL='http://static.cnbetacdn.com/article/2016/0227/ecabf0ffe6b82a2.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:83:"http://static.cnbetacdn.com/thumb/article/2016/0227/ecabf0ffe6b82a2.jpg_600x600.jpg";}}}}i:16;s:637:"
更重要的是,苹果可能有意让两款 iPad Pro 形成双旗舰 iPad 的组合。苹果自从推出 iPhone 6 和 iPhone 6 Plus 赚得盆满钵满后,双旗舰组合无疑让苹果尝到了甜头,在智能手机领域大行其道的双旗舰策略,很可能被苹果搬到 iPad 上。夸张地说,现在一部旗舰手机没有两个或以上的版本,都不好意思称之为旗舰。
苹果之前推出的 12.9 英寸 iPad Pro,很明显是针对那部分对于内容创作有需求的用户,而非普通用户。12.9 英寸的 iPad Pro 虽然轻便,但相比于 9.7 英寸版本的 iPad 还是稍显笨重。
";i:17;a:4:{s:3:"tag";s:1:"b";s:6:"option";N;s:8:"original";a:2:{i:0;s:3:"[B]";i:1;s:4:"[/B]";}s:8:"children";a:1:{i:0;s:6:"结语";}}i:18;s:647:"
虽然新款 iPad 的发布并不能改变平板市场低迷的局面,也无法挽救 iPad 的销量,但我们至少可以看出苹果对于 iPad 的态度:不轻易放弃。经过早几年的大杀四方后,现有的 iPad 产品线可能需要经历一次洗牌,一次变革才能回复昔日的活力。12.9 英寸的 iPad Pro 或许显得有些孤独,它无法凭借一己之力来让消费者重新认识 iPad,但假如加入 9.7 英寸版本,情况是否就会不一样了呢?在智能手机大获成功的双旗舰策略,在平板电脑市场上是否适用?这一切,还是需要时间和市场反映来证明。
";i:19;a:4:{s:3:"tag";s:1:"b";s:6:"option";N;s:8:"original";a:2:{i:0;s:3:"[B]";i:1;s:4:"[/B]";}s:8:"children";a:1:{i:0;s:7:"访问:";}}i:20;s:2:"
";i:21;a:4:{s:3:"tag";s:3:"url";s:6:"option";s:38:"http://aos.prf.hn/click/camref:100lcC/";s:8:"original";a:2:{i:0;s:46:"[URL='http://aos.prf.hn/click/camref:100lcC/']";i:1;s:6:"[/URL]";}s:8:"children";a:1:{i:0;s:26:"苹果在线商店(中国)";}}}, 1621686945, 1714743686
Run Time: 0.009551