Bug #12768 what are you doing?
Submitted: 23 Aug 2005 22:54 Modified: 23 Aug 2005 22:59
Reporter: Andrija Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:last OS:Any (any)
Assigned to: CPU Architecture:Any

[23 Aug 2005 22:54] Andrija 
Description:
I am porting my applications from mssql to mysql (actually enabling them to work on both databases) as I try to move at least some of my customers to mysql.
but I have a huge problem: rewrite all of sql queries which insert data into tables with date columns to enable mysql or ignore mysql.
Why: because you will not allow current_date to be set for datetime as default value (what is the big difference if timestamp can have current date as default value). And no, I don't want to update timestamp every time row is updated.
Damn, how do you intend to get new paying customers if you will not allow such important functionality? Do not bother replying. Just fix this unbelieveable lack of functionality.

How to repeat:
CREATE TABLE doesnotwork (dt datetime DEFAULT CURRENT_DATE)

Suggested fix:
Just fix this unbelieveable lack of functionality.
[23 Aug 2005 22:59] Jim Winstead 
Please do not submit the same bug more than once. An existing
bug report already describes this very problem. Even if you feel
that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments
to the original bug instead.

Thank you for your interest in MySQL.