On Wed, Nov 24, 2004 at 05:57:50PM +1100, Michael Knight wrote:
> Does this work as expected? When I run it I get:
>
> $ date --date '1081207440 seconds'
> date: invalid date `1081207440 seconds'
>
> and
>
> $ date --date '10 seconds'
> Thu Nov 25 21:42:30 EST 2004
>
> It seems the seconds
> [EMAIL PROTECTED] wrote:
>> You can also use the GNU date command:
>>
>> date --date '1081207440 seconds'
>
> Does this work as expected? When I run it I get:
thanks, everyone, for the solutions, most worked, except the above one:
# TZ=AEST python -c "import time; print time.ctime(108120
[EMAIL PROTECTED] wrote:
> You can also use the GNU date command:
>
> date --date '1081207440 seconds'
Does this work as expected? When I run it I get:
$ date --date '1081207440 seconds'
date: invalid date `1081207440 seconds'
and
$ date --date '10 seconds'
Thu Nov 25 21:42:30 EST 20
On Wed Nov 24, 2004 at 17:32:51 +1100, [EMAIL PROTECTED] wrote:
>On Wed, Nov 24, 2004 at 01:41:17PM +1100, Benno wrote:
>>
>> TZ=US/Pacific python -c "import time; print time.ctime(1081207440)"
>> ^
>
>You can also use the GNU date command:
>
> date --date '1081207440 seconds'
On Wed, Nov 24, 2004 at 01:41:17PM +1100, Benno wrote:
>
> TZ=US/Pacific python -c "import time; print time.ctime(1081207440)"
> ^
You can also use the GNU date command:
date --date '1081207440 seconds'
Prepend with a TZ setting if you so desire.
Matt
PS. perl: something
On Wed Nov 24, 2004 at 13:37:32 +1100, Michael Knight wrote:
>Voytek wrote:
>> is there some command line tool to do it for me (not inside MySQL) ?
>>
>> basically, I'm looking at some database dump, and, I need to find out what
>> was the date on ad hoc basis
>
>In addition to Benno's idea there
Voytek wrote:
> is there some command line tool to do it for me (not inside MySQL) ?
>
> basically, I'm looking at some database dump, and, I need to find out what
> was the date on ad hoc basis
In addition to Benno's idea there are also some web sites that provide
the feature that also let you c
On Wed Nov 24, 2004 at 13:29:11 +1100, Voytek wrote:
>
>
>> Hi Voytek,
>> Voytek Eymont wrote:
>
>> Yes, that's a Unix timestamp (number of seconds from January 1, 1970).
>> In MySQL you can easily convert these to a readable date using its
>> FROM_UNIXTIME function, which you can read more about h
> Hi Voytek,
> Voytek Eymont wrote:
> Yes, that's a Unix timestamp (number of seconds from January 1, 1970).
> In MySQL you can easily convert these to a readable date using its
> FROM_UNIXTIME function, which you can read more about here:
>
> http://dev.mysql.com/doc/mysql/en/Date_and_time_func
This one time, at band camp, Voytek Eymont wrote:
>I'm looking at some date/time values in an MySQL tables that are
>represented like:
>1076022093 1076020027 1081207440
>are these... the *nix seconds things ?
They sure look like it! As far as I know, MySQL stores dates as integers,
by converting
Hi Voytek,
Voytek Eymont wrote:
> I'm looking at some date/time values in an MySQL tables that are
> represented like:
> 1076022093 1076020027 1081207440
> are these... the *nix seconds things ?
>
> how can I interactively convert a single value to human readable format ?
Yes, that's a Unix time
I'm looking at some date/time values in an MySQL tables that are
represented like:
1076022093 1076020027 1081207440
are these... the *nix seconds things ?
how can I interactively convert a single value to human readable format ?
--
Voytek
--
SLUG - Sydney Linux User's Group Mailing List - http:
12 matches
Mail list logo
