Hmm, weird. Because I have actually used Date before, and had the time
dropped off.
Maybe it has something to do with the JDBC drivers conversion of
java.util.Date -> jdbc type DATE -> SQL type DATE?
Ohwell, it works as timestamp, so I won't worry about it for now.
Thanks for the info,
-Davi
David Budworth wrote:
[EMAIL PROTECTED]">
Or does PostgreSQL DATE/TIMESTAMP exactly the same? I know oracle willdrop the time portion if the column type is DATE.-David
Actually Oracle will not drop the time protion if the column type
is DATE. The following is from the Oracle 8 manual. Orac
Don't worry, I already set it to TIMESTAMP.
I am a little put off by Adam changing the default database mapping in
his deb package. It is his choice to do this, but I will recommend to
everyone that they don't use the deb package for this reason.
-dain
David Budworth wrote:
> The problem h
The problem here is that java.util.Date holds an actualy time/date.
If you don't map it to TIMESTAMP, then you have a dataloss.
If you want a real SQL DATE field, then use java.sql.Date (which is
a java.util.Date with the time suppressed)
I think it would be bad policy to make the default data
On Tue, 12 Feb 2002, Dain Sundstrom wrote:
> This is for anyone who knows Postgres out there,
>
> There is a patch at sf that suggest adding the following mapping:
>
>
>java.util.Date
>TIMESTAMP
>TIMESTAMP
>
>
> There is currently no mapping for java.util.Date, but there is a mappin
This is for anyone who knows Postgres out there,
There is a patch at sf that suggest adding the following mapping:
java.util.Date
TIMESTAMP
TIMESTAMP
There is currently no mapping for java.util.Date, but there is a mapping
for java.sql.Date, which is:
java.sql.Date
DATE
