"Peter Eisentraut" <[EMAIL PROTECTED]> writes: > The clarity stems from the fact that this is the variant that doesn't > lose data whereas the other one does.
I think double has a wider range. So you get a choice between losing precision or not being able to store all values. > The expression I originally posted works on Oracle. I wonder how they > do it. I think they only have one type which uses different storage formats depending on the data. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support! ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
