Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 31353 invoked from network); 16 Jun 2005 02:51:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 16 Jun 2005 02:51:29 -0000 Received: (qmail 97346 invoked by uid 500); 16 Jun 2005 02:51:25 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 97314 invoked by uid 500); 16 Jun 2005 02:51:25 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 97298 invoked by uid 99); 16 Jun 2005 02:51:25 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from ajax-1.apache.org (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 15 Jun 2005 19:51:23 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 7781E458 for ; Thu, 16 Jun 2005 01:14:50 +0200 (CEST) Message-ID: <1573905829.1118877290488.JavaMail.jira@ajax.apache.org> Date: Thu, 16 Jun 2005 01:14:50 +0200 (CEST) From: "Jack Klebanoff (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-355) Document TIMESTAMPADD and TIMESTAMPDIFF functions In-Reply-To: <1980281437.1118718167659.JavaMail.jira@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/DERBY-355?page=comments#action_12313762 ] Jack Klebanoff commented on DERBY-355: -------------------------------------- The latest patch looks good to me. In my previous comments I agreed with the decision to put TIMESTAMPADD and TIMESTAMPDIFF in the builtin function section. Users are more likely to find them there than in the JDBC escape section. The other JDBC escape features have equivalent functionality in pure SQL. Users looking through the Derby SQL reference will find the functionality and be able to get their jobs done. I think that the JDBC escapes are a bit obscure, users looking for timestamp arithmetic may not think of looking in the JDBC escape section. The JDBC escape section should have at least a reference to TIMESTAMPADD and TIMESTAMPDIFF. We can document them in the builtin function section and have references in the JDBC escape section, or document them in the JDBC escape section and have references in the builtin function section. I think that it is important that both sections mention the functions. > Document TIMESTAMPADD and TIMESTAMPDIFF functions > ------------------------------------------------- > > Key: DERBY-355 > URL: http://issues.apache.org/jira/browse/DERBY-355 > Project: Derby > Type: Sub-task > Components: Documentation > Environment: all > Reporter: Jeff Levitt > Assignee: Jeff Levitt > Priority: Minor > Fix For: 10.1.0.0 > Attachments: derby355finaldraft2.zip > > Derby 81 (parent task to this issue) needs to be documented. TIMESTAMPADD and TIMESTAMPDIFF need to be included in the reference manual with the built-in functions. I created a patch for this which I will attach to this issue for review. I used http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbctime__date__and_interval_functions.asp > as my specification. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira