oracle中CURRENT_TIMESTAMP和SYSDATE不同

Different CURRENT_TIMESTAMP and SYSDATE in oracle(oracle中CURRENT_TIMESTAMP和SYSDATE不同)
本文介绍了oracle中CURRENT_TIMESTAMP和SYSDATE不同的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在 oracle 10g 中执行此 SQL 后:

After executing this SQL in oracle 10g:

SELECT SYSDATE, CURRENT_TIMESTAMP  FROM DUAL

我收到这个奇怪的输出:

I receive this strange output:

时间差的原因是什么?服务器时间等于 SYSDATE 值

What is cause of the difference in time? The server time is equal of SYSDATE value

推荐答案

CURRENT_DATECURRENT_TIMESTAMP 返回会话时区中的当前日期和时间.

CURRENT_DATE and CURRENT_TIMESTAMP return the current date and time in the session time zone.

SYSDATESYSTIMESTAMP 返回系统日期和时间 - 即数据库所在的系统.

SYSDATE and SYSTIMESTAMP return the system date and time - that is, of the system on which the database resides.

如果您的客户端会话与数据库所在的服务器不在同一个时区(或者说它不是,通过您的 NLS 设置),混合 SYS*CURRENT_* 函数将返回不同的值.他们都是对的,他们只是代表不同的东西.看起来您的服务器处于(或认为是)+4:00 时区,而您的客户端会话处于 +4:30 时区.

If your client session isn't in the same timezone as the server the database is on (or says it isn't anyway, via your NLS settings), mixing the SYS* and CURRENT_* functions will return different values. They are all correct, they just represent different things. It looks like your server is (or thinks it is) in a +4:00 timezone, while your client session is in a +4:30 timezone.

如果时钟不同步,您可能还会看到时间上的微小差异,这在这里似乎不是问题.

You might also see small differences in the time if the clocks aren't synchronised, which doesn't seem to be an issue here.

这篇关于oracle中CURRENT_TIMESTAMP和SYSDATE不同的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!

本站部分内容来源互联网,如果有图片或者内容侵犯您的权益请联系我们删除!

相关文档推荐

Execute complex raw SQL query in EF6(在EF6中执行复杂的原始SQL查询)
Hibernate reactive No Vert.x context active in aws rds(AWS RDS中的休眠反应性非Vert.x上下文处于活动状态)
Bulk insert with mysql2 and NodeJs throws 500(使用mysql2和NodeJS的大容量插入抛出500)
Flask + PyMySQL giving error no attribute #39;settimeout#39;(FlASK+PyMySQL给出错误,没有属性#39;setTimeout#39;)
auto_increment column for a group of rows?(一组行的AUTO_INCREMENT列?)
Sort by ID DESC(按ID代码排序)