Discussion on:

Optimize your databases with PostgreSQL data types

The download version of this article is available here:
http://techrepublic.com.com/5138-9592-5911159.html

What other data types would you include in this document?

-32,000 , + 32000 approx.
Lord luv us and save us.
What is this dumbing down day ?
No point in saying -32768 to +32767 they won't know why anyway ?

To be quite honest I tend to use integers all the time, lost count of the number of times I've got stiffed with the scenario 'It's numeric code of 1 to a 100'

Three weeks later
When I try to put the misc code in there it says -999 won't fit.

Three seconds later
I'll come back when you've calmed down.

I don't like floating points either, some times they are unavoidable but if they are avoid 'em. Don't store tonnes to three decimal places, store kilos.
Nothing more annoying than someone wanting you to explain why the totals on his excel download don't match those off the system, three kilos off in 6,000,000 tones is ok, two different numbers from the 'same' data never is.

... as a GIS person, i'd vote for including a teratise on teh Geometry types, but I think if I'm honest it might be too specialised for this forum

how example with coding for timestamp???