| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Hartmut Benz <hartmut(dot)benz(at)ti-wmc(dot)nl> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Small addition to PGInterval |
| Date: | 2007-04-11 07:53:35 |
| Message-ID: | Pine.BSO.4.64.0704110347270.5256@leary.csoft.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Thu, 29 Mar 2007, Hartmut Benz wrote:
> please find attached a small extension to PGInterval:
> - getTimeInMillis - returns the number of milliseconds in the interval
getLengthInMillis doesn't account for months.
ONE_YEAR is seconds in a year instead of milliseconds.
Shouldn't we use the server's definition instead of google's for a year's
length in seconds:
select extract(epoch from '1 year'::interval);
date_part
-----------
31557600
(1 row)
> - copying constructor PGInterval(PGInterval) for type-safe, cast-free cloning
> - now implements Comaparable<PGInterval>
We can't use generics in this class because it must be buildable with
older JDK versions.
Also context diffs (-c) are preferred.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc Mamin | 2007-04-11 08:12:14 | Re: Encoding issue (utf8): different strings received from java than from PGAdmin |
| Previous Message | Kris Jurka | 2007-04-10 17:57:27 | Re: Exception in running query |