Hiya.
I'm looking for some design advice.
I have a number of tables whose data consist of configuration details
and parameters that are incorporated into config files for various
server applications. For example, a table of customers' email address
forwarding info, so a PHP application can be
On Sunday 26 January 2003 17:02, Paul Chvostek wrote:
So what's the best way to store a date? I've always liked storing epoch
seconds as INTs, and leaving the translation to/from a human-readable
date up to the application, but aside from the relative unreadability of
this, are there any
[snip]
Would I be better off spending a few bytes extra per record and
storing
things as DATETIME rather than an INT? If I'm looking at the
possibily
making the application more database-portable in the future, are there
gotchas I should be aware of with any particular field types?
This has
