dedecms用mysql，为什么调用FROM_UNIXTIME(postdate)不出来呢？

Question

{dede:sql sql='SELECT tid,FROM_UNIXTIME(postdate) FROM `pw_threads` ORDER BY `pw_threads`.`tid` DESC LIMIT 0 , 30'}
[field:postdate /]<br />
{/dede:sql}我测试了很久，都没弄明白错出在哪里》。。

Answer 1

你的postdate是什么字段类型？desc `pw_threads`  贴出来看一下。

Answer 2

mysql> desc `pw_threads`;
+------------+-----------------------+------+-----+---------+----------------+
| Field      | Type                  | Null | Key | Default | Extra          |
+------------+-----------------------+------+-----+---------+----------------+
| tid        | mediumint(8) unsigned | NO   | PRI | NULL    | auto_increment |
| fid        | smallint(6) unsigned  | NO   | MUL | 0       |                |
| icon       | tinyint(2)            | NO   |     | 0       |                |
| titlefont  | varchar(15)           | NO   |     |         |                |
| author     | varchar(15)           | NO   |     |         |                |
| authorid   | mediumint(8) unsigned | NO   | MUL | 0       |                |
| subject    | varchar(100)          | NO   |     |         |                |
| toolinfo   | varchar(16)           | NO   |     |         |                |
| toolfield  | varchar(21)           | NO   |     |         |                |
| ifcheck    | tinyint(1)            | NO   |     | 0       |                |
| type       | tinyint(2)            | NO   |     | 0       |                |
| postdate   | int(10) unsigned      | NO   | MUL | 0       |                |
| lastpost   | int(10) unsigned      | NO   |     | 0       |                |
| lastposter | varchar(15)           | NO   |     |         |                |
| hits       | int(10) unsigned      | NO   |     | 0       |                |
| replies    | int(10) unsigned      | NO   |     | 0       |                |
| topped     | smallint(6)           | NO   |     | 0       |                |
| locked     | tinyint(1)            | NO   |     | 0       |                |
| digest     | tinyint(1)            | NO   | MUL | 0       |                |
| special    | tinyint(1)            | NO   | MUL | 0       |                |
| state      | tinyint(1)            | NO   |     | 0       |                |
| ifupload   | tinyint(1)            | NO   |     | 0       |                |
| ifmail     | tinyint(1)            | NO   |     | 0       |                |
| if     | smallint(6)           | NO   |     | 0       |                |
| ifshield   | tinyint(1)            | NO   |     | 0       |                |
| anonymous  | tinyint(1)            | NO   |     | 0       |                |
| dig        | int(10)               | NO   |     | 0       |                |
| fight      | int(10)               | NO   |     | 0       |                |
| ptable     | tinyint(3)            | NO   |     | 0       |                |
| ifmagic    | tinyint(1)            | NO   |     | 0       |                |
| ifhide     | tinyint(1)            | NO   |     | 0       |                |
| inspect    | varchar(30)           | NO   |     |         |                |
+------------+-----------------------+------+-----+---------+----------------+
32 rows in set (0.01 sec)mysql>

Answer 3

在MYSQL中直接执行SELECT tid,FROM_UNIXTIME(postdate) FROM `pw_threads` ORDER BY `pw_threads`.`tid` DESC LIMIT 0 , 30; 是否正常？

Answer 4

mysql> SELECT tid,FROM_UNIXTIME(postdate) FROM `pw_threads` ORDER BY `pw_threads
`.`tid` DESC LIMIT 0 , 30;
+-------+-------------------------+
| tid   | FROM_UNIXTIME(postdate) |
+-------+-------------------------+
| 12292 | 2010-01-07 13:10:13     |
| 12291 | 2010-01-03 17:37:13     |
| 12290 | 2010-01-02 19:58:45     |
| 12199 | 2009-12-31 10:15:30     |
| 12198 | 2009-12-31 10:15:10     |
| 12197 | 2009-12-31 10:14:39     |
| 12196 | 2009-12-31 10:14:18     |
| 12195 | 2009-12-31 10:13:50     |
| 12194 | 2009-12-31 10:13:03     |
| 12193 | 2009-12-31 10:12:36     |
| 12192 | 2009-12-31 10:10:33     |
| 12191 | 2009-12-31 10:09:56     |
| 12190 | 2009-12-31 10:09:15     |
| 12084 | 2009-12-31 02:50:30     |
| 11499 | 2009-12-24 03:55:47     |
| 11346 | 2009-12-22 06:17:21     |
| 11339 | 2009-12-21 22:30:07     |
| 11250 | 2009-12-19 10:27:01     |
| 11249 | 2009-12-19 10:26:30     |
| 11248 | 2009-12-19 10:26:01     |
| 11247 | 2009-12-19 10:25:36     |
| 11246 | 2009-12-19 10:20:34     |
| 11245 | 2009-12-19 10:19:48     |
| 11244 | 2009-12-19 10:19:11     |
| 11243 | 2009-12-19 10:18:48     |
| 11242 | 2009-12-19 10:17:26     |
| 11241 | 2009-12-19 10:16:53     |
| 11240 | 2009-12-19 10:16:22     |
| 11239 | 2009-12-19 10:15:55     |
| 11238 | 2009-12-19 10:15:30     |
+-------+-------------------------+
30 rows in set (0.02 sec)mysql>正常，不管是
{dede:sql sql='SELECT tid,FROM_UNIXTIME(postdate) FROM `pw_threads` ORDER BY `pw_threads`.`tid` DESC LIMIT 0 , 30'} 
[field:postdate /] <br /> 
{/dede:sql} 还是
{dede:sql sql='SELECT tid,FROM_UNIXTIME(postdate) FROM `pw_threads` ORDER BY `pw_threads`.`tid` DESC LIMIT 0 , 30'} 
[field:FROM_UNIXTIME(postdate) /] <br /> 
{/dede:sql}都不行。。

Answer 5

不懂 dedecms ，只知道MYSQL。现在显然问题不在MYSQL上。估计你的这个dedecms对提交的SQL语句做了什么改动。你可以打开MYSQL的日志，看看dedecms提交的到底是什么SQL语句。 但根子是dedecms上。

Answer 6

MYSQL的日志？MYSQL的日志在哪里看的呢？