> I need to create a "commands" table. A program will periodically check
on this table whether
> there's a pending command for it to execute or not. Whatever the reason,
this program might read a command but not acknowledge it's
> Other program will check out whether the command timeout has expired or
not and so act accordingly.
> I guess I can use some sort of integer in order to represent it as a
unix timestamp, but I would prefer to use a "timestamp".
As I said -- to store date/time values, you should NOT use
the TIMESTAMP datatype, cause it isn't supposed to be
used to store custom date/time values.
I suggest you read the documentation on MySQL Date/Time
datatypes -- it has a fine explanation of what to use and what
to use the TIMESTAMP datatype for.
Don't bother going the Unix integer timestamp thingy route.
Just read this:
Database Workbench - development tool for MySQL, and more!
Database development questions? Check the forum!