| From: | <Charles(dot)McDevitt(at)emc(dot)com> |
|---|---|
| To: | <josh(at)agliodbs(dot)com>, <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | <wmoran(at)potentialtech(dot)com>, <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Why don't we accept exponential format for integers? |
| Date: | 2010-12-17 22:29:44 |
| Message-ID: | 816A162DFA20D547AAE6C05FD3CFFAC605BA57DE50@MX06A.corp.emc.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > And so does:
> > SELECT 1.23e+01::Integer
> >
> >
> >> > which I find just as dangerous as
> >> > SELECT '1.234e+01'::Integer;
> >
> > Add quotes to either of the other two, and then they don't work either.
>
> Well, that's stupidly arbitrary. If we're not going to accept
> '1.234e+01'::Integer, then we shouldn't accept 1.234e+01::Integer either.
>
Isn't this a case of an explicit cast? Shouldn't our answer to 1.234e+1::Integer be the same as CAST(1234e+1 AS Integer)?
Which is legal ISO SQL, as far as I can see.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2010-12-17 23:09:50 | Re: Why don't we accept exponential format for integers? |
| Previous Message | Marti Raudsepp | 2010-12-17 22:27:23 | Re: Why don't we accept exponential format for integers? |