+6  A: 

No you can't, and it would be a bad idea if you could. Every timestamp in your database is going to use the same space, regardless of how big the number is. (Assuming you are storing the number as a number and not as a string or something.)

Now, if you really want this, you'll have to write it yourself. I.e. subtract the time from your timestamps before putting them into the database, and add the time to the timestamps when you get them back out. But this is asking for maintenance problems. (In fact, using timestamps instead of the database's native DATETIME datatype is asking for problems.)

Kip
Actually, integers can be compressed using 7-bit encoding, so that values 0 <= x <= (2^7-1) use one byte, (2^7) <= x <= (2^14-1) uses two bytes, etc, which is useful when CPU is cheaper than I/O and you expect most numbers won't be huge.
gustafc
Which, btw, does not detract from your main point about the wiseness of using the database's DATETIME. But, if you were to do something like this, I'd start by looking for some setting in the database rather than one in the application platform.
gustafc