[jira] [Commented] (DERBY-6834) support for CURRENT_TIMESTAMP(precision) appears to be missing

[ https://issues.apache.org/jira/browse/DERBY-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14742507#comment-14742507 ] Rick Hillegas commented on DERBY-6834: -- Note that CURRENT_TIME has the same optional precision

[jira] [Commented] (DERBY-6834) support for CURRENT_TIMESTAMP(precision) appears to be missing

[ https://issues.apache.org/jira/browse/DERBY-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14740851#comment-14740851 ] Bryan Pendleton commented on DERBY-6834: Ah, I see, thank you. Accepting (and ignoring) the

[jira] [Commented] (DERBY-6834) support for CURRENT_TIMESTAMP(precision) appears to be missing

[ https://issues.apache.org/jira/browse/DERBY-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14740003#comment-14740003 ] Bryan Pendleton commented on DERBY-6834: To be explicit, what would be different about your new

[jira] [Commented] (DERBY-6834) support for CURRENT_TIMESTAMP(precision) appears to be missing

[ https://issues.apache.org/jira/browse/DERBY-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14740051#comment-14740051 ] Rick Hillegas commented on DERBY-6834: -- The syntax for CURRENT_TIMESTAMP() is defined in the 2011 SQL

[jira] [Commented] (DERBY-6834) support for CURRENT_TIMESTAMP(precision) appears to be missing

[ https://issues.apache.org/jira/browse/DERBY-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14740229#comment-14740229 ] Julian Reschke commented on DERBY-6834: --- The main point is that the syntax should be accepted, so