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 execution. 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".
Any suggestions? Kind regards ----Mensaje original---- De: [EMAIL PROTECTED] Recibido: 10/04/2006 11:51 Para: <[EMAIL PROTECTED]>, <mysql@lists.mysql.com> Asunto: Re: timestamp & not null Hi, > I created a table and, into it, a timestamp field: > ... EXPIRES TIMESTAMP NOT NULL, ... > > When I issue the command "describe" it shows the field "expires" allows nulls and defaults to CURRENT_TIMESTAMP. Also, each time I update > a field other than "expires" in this table, "expires" gets updated to the current timestamp. > > Does anybody know how can I make a timestamp field be "not null"? > Lots of thanks to you all. If you want to store date/time values, do not use the TIMESTAMP datatype. What is it that you're trying to do? Martijn Tonies Database Workbench - development tool for MySQL, and more! Upscene Productions http://www.upscene.com My thoughts: http://blog.upscene.com/martijn/ Database development questions? Check the forum! http://www.databasedevelopmentforum.com Prueba el Nuevo Correo Terra; Seguro, Rápido, Fiable. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
