Received: from candle.pha.pa.us (root@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id NAA37953 for ; Tue, 13 Jul 1999 13:02:13 -0400 (EDT) (envelope-from maillist@candle.pha.pa.us) Received: (from maillist@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id MAA25778; Tue, 13 Jul 1999 12:57:24 -0400 (EDT) From: Bruce Momjian Message-Id: <199907131657.MAA25778@candle.pha.pa.us> Subject: Re: [SQL] Problem with timestamp and primary key. In-Reply-To: <378AE74F.C804CB78@tissat.es> from Esteban Chiner Sanz at "Jul 13, 1999 09:14:23 am" To: Esteban Chiner Sanz Date: Tue, 13 Jul 1999 12:57:24 -0400 (EDT) CC: pgsql-sql@postgreSQL.org X-Mailer: ELM [version 2.4ME+ PL56 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > Does anybody know what could be the problem. What should I do? > The problem is that I could subtitute TIMESTAMP with DATE or DATETIME > but that's not compatible with Oracle's DATE and, when I try to access > the table with JDBC in Oracle works fine but in Postgres it needs to be > Timestamp. > Please help, This is a known problem because our jdbc does not know DATETIME, and our TIMESTAMP can't do indexes. People, any solutions? -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026