From: | Henry Drexler <alonup8tb(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | integer instead of 'double precision'? |
Date: | 2011-09-09 14:42:11 |
Message-ID: | CAAtgU9QHTCei4Z3N2QTdfokdON50=yWkK4iTUQTicxgFY9-inQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
take any table and run
Query
---------------------
select
1/3
from
storage
limit 1
Result
---------------------
?column?
integer
0
Expected Result
---------------------
?column?
double precision
0.33333...
Question
---------------------
Since there is no column type to begin with as this is a made-up column,
shouldn't postgres know it is double precision due to the remainder?
I thought perhaps I could cast it as double precision as noted on
http://www.postgresql.org/docs/8.3/interactive/sql-expressions.html
though doing the following:
select
float8(1/3)
from
storage
limit 1
results in:
float8
double precision
0
any ideas on how to get this type of a manufactured column (not sure the
right term for it) to show the double precision result?
From | Date | Subject | |
---|---|---|---|
Next Message | Henry Drexler | 2011-09-09 15:07:48 | Re: integer instead of 'double precision'? |
Previous Message | Raymond O'Donnell | 2011-09-09 08:32:56 | Re: PSQLRestore |