Re: update and times

2010-10-07 Thread Simcha Younger
On Wed, 06 Oct 2010 17:48:55 -0400 kalin m wrote: > > > Simcha Younger wrote: > >> executing this query didn't update the record. > >> > >> why? > >> > > The two values you have here are equal: > > sample data : 12862162510269684 > > query: where unix_time < 1286216251026

Re: update and times

2010-10-06 Thread kalin m
Simcha Younger wrote: On Mon, 04 Oct 2010 16:11:08 -0400 kalin m wrote: what i'm trying to do is update the column only of one of those times isn't yet passed. and it works. except sometimes... like these 2 unix times: this was in the table under unix time: 12862162385941345... t

Re: update and times

2010-10-05 Thread Simcha Younger
On Mon, 04 Oct 2010 16:11:08 -0400 kalin m wrote: > > > what i'm trying to do is update the column only of one of those times > isn't yet passed. and it works. except sometimes... > > like these 2 unix times: > > this was in the table under unix time: 12862162385941345... > > this 1286216

Re: update and times

2010-10-04 Thread kalin m
right the unix times in the example table were just that - examples from a few days ago... the example with the query was a 'real one' something that happened today... it's a 64 bit machine. the unix times are stored in a bigint column. the times in the column and the update statement

RE: update and times

2010-10-04 Thread Gavin Towey
Those unix_time values don't seem to correspond to the dates you have. select NOW(), UNIX_TIMESTAMP(NOW()); +-+---+ | NOW() | UNIX_TIMESTAMP(NOW()) | +-+---+ | 2010-10-04 13:18:08 |1286223488