From derby-user-return-2134-apmail-db-derby-user-archive=db.apache.org@db.apache.org Mon Sep 26 22:15:27 2005 Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 34573 invoked from network); 26 Sep 2005 22:15:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 26 Sep 2005 22:15:26 -0000 Received: (qmail 82454 invoked by uid 500); 26 Sep 2005 22:12:53 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 81947 invoked by uid 500); 26 Sep 2005 22:12:48 -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 81723 invoked by uid 99); 26 Sep 2005 22:12:46 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Sep 2005 15:12:46 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [192.18.98.36] (HELO brmea-mail-4.sun.com) (192.18.98.36) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Sep 2005 15:12:51 -0700 Received: from phys-epost-1 ([129.159.136.14]) by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id j8QMCIvD004571 for ; Mon, 26 Sep 2005 16:12:18 -0600 (MDT) Received: from conversion-daemon.epost-mail1.sweden.sun.com by epost-mail1.sweden.sun.com (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) id <0ING00B011Y6WD@epost-mail1.sweden.sun.com> (original mail from Bernt.Johnsen@Sun.COM) for derby-user@db.apache.org; Tue, 27 Sep 2005 00:12:18 +0200 (MEST) Received: from localhost (vpn-129-159-115-202.Norway.Sun.COM [129.159.115.202]) by epost-mail1.sweden.sun.com (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) with ESMTP id <0ING0093L30HG6@epost-mail1.sweden.sun.com> for derby-user@db.apache.org; Tue, 27 Sep 2005 00:12:18 +0200 (MEST) Date: Tue, 27 Sep 2005 00:14:25 +0200 From: "Bernt M. Johnsen" Subject: Re: Derby dates In-reply-to: <433848CB.8050001@neometsys.fr> To: Derby Discussion Message-id: <20050926221425.GA9209@barbar.sun.com> Organization: Sun Microsystems MIME-version: 1.0 Content-type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary=xHFwDpU9dbj6ez1V Content-disposition: inline User-Agent: Mutt/1.5.9i References: <4337E68E.9080606@neometsys.fr> <20050926134414.GB30714@atum01.norway.sun.com> <433848CB.8050001@neometsys.fr> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable >>>>>>>>>>>> Nicolas Dufour wrote (2005-09-26 15:15:23): > Bernt M. Johnsen wrote: >=20 > > > >{ts 'yyyy-mm-dd hh:mm:ss.f...'} > > > >Which should work for any conformat JDBC driver > >=20 > > > so any other format like mm/dd/yyyy hh:mm:ss for example will not be=20 > inserted right ??? > or is it a way to avoid this problem ? Both the JDBC escape format {ts 'yyyy-mm-dd hh:mm:ss'} and the Derby builtin timestamp('yyyy-mm-dd hh:mm:ss') is conformant with ISO-8601 The escape format is conformant with the JDBC spec The builtin is nearly conformant with the SQL standard=20 (it should have been=20 timestamp 'yyyy-mm-dd hh:mm:ss' =2E...) Any other date/time syntax will need to be converted by some means.=20 Note however that there also are the classes java.sql.Date java.sql.Time java.sql.Timestamp which may be used to insert dates/times into Derby --=20 Bernt Marius Johnsen, Database Technology Group,=20 Sun Microsystems, Trondheim, Norway --xHFwDpU9dbj6ez1V Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.7 (GNU/Linux) iD8DBQFDOHLBlFBD9TXBAPARAszuAJ0SLOtF1bxjW4kF096aConMxbjTHgCgkY87 WlEbBONY/QrbCealrjHmBhU= =nXGa -----END PGP SIGNATURE----- --xHFwDpU9dbj6ez1V--