Bug #12562 sysdate() not behaving according to Oracle behavior

• Submitted: 13 Aug 2005 0:05
• Modified: 26 Aug 2005 19:54
• Reporter: Brian Aker
• Status: Closed
• Category: MySQL Server
• Severity: S3 (Non-critical)
• Assigned to: Jim Winstead
• CPU Architecture: Any

[13 Aug 2005 0:05] Brian Aker

Description:
Once Monty finishes http://bugs.mysql.com/bug.php?id=12480, please modify the sysdate() call to correctly emulate Oracle's sysdate() call. Currently sysdate() is behaving correctly to Oracle, but after the changes to now() it will no longer. 

How to repeat:
Run sysdate, and you will find that it does not have the correct behavior :)

[18 Aug 2005 0:20] Bugs System

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/28425

[23 Aug 2005 0:16] Bugs System

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/28661

[24 Aug 2005 22:51] Bugs System

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/28783

[25 Aug 2005 0:14] Jim Winstead

Fixed in 5.0.13.

[26 Aug 2005 19:54] Paul DuBois

Noted in 5.0.13 changelog, functions chapter.

[10 Mar 2006 14:09] Bugs System

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/3708

[10 Mar 2006 14:48] Bugs System

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/3710