Will a 'null' timestamp take up as much space as an initialized timestamp? I'm thinking of new rows, not adding a timestamp column to an existing table.
What's the easiest way to build a where clause based on a unix timestamp on app side when I have separate date and time fields? seems a bit slow to do: where date>=from_unixtime... and date=from_un