Re: Why TimeStamp was truncated? On 28 Feb, 16:05, "Rik Wasmus" <luiheidsgoe...@hotmail.com> wrote:
> On Thu, 28 Feb 2008 16:58:50 +0100, howa <howac...@gmail.com> wrote:
> > On 2$B7n(B28$BF|(B, $B2<8a(B6$B;~(B48$BJ,(B, "Rik Wasmus" <luiheidsgoe...@hotmail.com> wrote:
> >> On Thu, 28 Feb 2008 11:43:18 +0100, howa <howac...@gmail.com> wrote:
> >> > CREATE TABLE `table1` (
> >> > `ts` TIMESTAMP NOT NULL
> >> > ) ENGINE = innodb;
>
> >> > INSERT INTO `table1` (`ts`) VALUES ('1202832067');
> >> > INSERT INTO `table1` (`ts`) VALUES ( UNIX_TIMESTAMP('1202832067') );
>
> >> > The table result is storing "0000-00-00 00:00:00" for both queries,
> >> > any idea?
>
> >> Because MySQL doesn't automatically convert an integer to a datetime
> >> string.
> >> INSERT INTO `table1` (`ts`) VALUES ( FROM_UNIXTIME('1202832067') );
>
> > Hello, If I have millions of row of UNIX timestamps to insert, I don't
> > want to invoke the method everytime, are there any faster method?
>
> Add an int column ('timestampcolumn') to the table, load it in there, and
> then run:
> UPDATE table SET datetimecolumn = FROM_UNIXTIME(timestampcolumn);
> --
> Rik Wasmus
But this still invokes the method once per row. |