| From: | Thomas Lockhart <lockhart(at)fourpalms(dot)org> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: EXTRACT broken |
| Date: | 2001-10-15 05:34:12 |
| Message-ID: | 3BCA7554.4BF7A573@fourpalms.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > Oh yeah. We don't have a date_part(units, time) function defined, so it
> > is getting converted to interval (which in other contexts *does* have
> > some usefulness as a "time equivalent").
> You're going to have an extremely hard time convincing me of that.
OK, thanks for the warning. I'll try later when I have more time...
> > We could fairly easily define a date_part() for the time and timetz data
> > types.
> I had figured that time would be cast to timestamp. Which is probably
> what it used to do.
Tom Lane pointed out the problem of inferring an appropriate date for
the upcast.
- Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2001-10-15 08:55:58 | Re: New contrib/tsearch module for 7.2 |
| Previous Message | Thomas Lockhart | 2001-10-15 05:31:58 | Re: How do I get the current time in seconds in the unix |