From derby-user-return-13558-apmail-db-derby-user-archive=db.apache.org@db.apache.org Tue May 3 11:52:58 2011 Return-Path: X-Original-To: apmail-db-derby-user-archive@www.apache.org Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B3ABDDAD for ; Tue, 3 May 2011 11:52:58 +0000 (UTC) Received: (qmail 45178 invoked by uid 500); 3 May 2011 11:52:58 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 45146 invoked by uid 500); 3 May 2011 11:52:58 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 45139 invoked by uid 99); 3 May 2011 11:52:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 May 2011 11:52:58 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lukas.eder@gmail.com designates 209.85.214.44 as permitted sender) Received: from [209.85.214.44] (HELO mail-bw0-f44.google.com) (209.85.214.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 May 2011 11:52:50 +0000 Received: by bwz13 with SMTP id 13so29350bwz.31 for ; Tue, 03 May 2011 04:52:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=zTTsmi2PNswUEEng6HHCX7mKiMNXevCMnFSGyVa81vw=; b=PHIPz6aKZv2FS46TJ1AGDihgDVq2IjCXMsJJDzzuXPW8VPfoen2+6ZzySOAAu+yFjj GMZw8qioG5fHoKzc+qU2XkA74SM2O8u1IWeRa4uQ4VRR83zrla0S3FwccRuWmrkQfvh7 /rBK2N+yK+G0y+u+IFodwpCFHyiliCjmgZQ0w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=BulyKlMiIix640h8O27Wy4rziBFNi/4VNTfK0lX9e8M1h2MRZD48S3vNBX7VfXHXUo zLvI/bNwURefoAkwf5/lmKV1ABaF9+dvqGeadcxcH0FReO+zIqJ2Qrv/xF+n5Ixgqtby HB/JFqOa+LjDAhLVkYtisqBxLxEY0BpFNRCkc= MIME-Version: 1.0 Received: by 10.205.24.9 with SMTP id rc9mr967621bkb.92.1304423550570; Tue, 03 May 2011 04:52:30 -0700 (PDT) Received: by 10.204.59.148 with HTTP; Tue, 3 May 2011 04:52:30 -0700 (PDT) In-Reply-To: References: Date: Tue, 3 May 2011 13:52:30 +0200 Message-ID: Subject: Re: Date manipulation in Derby From: Lukas Eder To: derby-user@db.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org > Derby supports the JDBC escape function TIMESTAMPADD, documented here: > http://db.apache.org/derby/docs/10.8/ref/rrefjdbc88908.html > > Example: > > ij> values {fn timestampadd(SQL_TSI_DAY, 1, timestamp('2010-12-31 23:59:59'))}; Are there any plans to make this function available in a more regular syntax? Or what are the reasons that this is only possible using this "JDBC escape function" syntax? I'd expect this to be possible too: timestampadd(SQL_TSI_DAY, 1, timestamp('2010-12-31 23:59:59'))