| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "PostgreSQL Development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Which casts should be implicit |
| Date: | 2002-07-26 05:49:04 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOMEFOCDAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > date -> timestamp[tz]: I'm suspicious of this one, but it's hard to
> > explain. The definition to fill in the time component with zeros is
> > reasonable, but it's not the same thing as casting integers to floats
> > because dates really represent a time span of 24 hours and timestamps an
> > indivisible point in time. I suggest making this non-implicit, for
> > conformance with SQL and for general consistency between the date/time
> > types.
>
> Althought I'm sure there's _loads_ of people using this conversion,
> including me in various random places in the codebase.
Actually, if inserting counts as an explicit conversion, then maybe not...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2002-07-26 06:12:05 | Re: Proposal: anonymous composite types for Table Functions |
| Previous Message | Cameron Hutchison | 2002-07-26 03:21:50 | Re: CREATE SYNONYM suggestions |