like to convert unix timestamp into human readable date.
Obviously Access doesn't have mysql *FROM_UNIXTIME(unix_timestamp)*
function.
So: may someone know a reference to the function algorithm?
Or can someone tell me how can i use mysql functions into MSAccess?
Thank you in advance...
|
system the following command returns this:
mysql> SELECT FROM_UNIXTIME(-100);
+-+
| FROM_UNIXTIME(-100) |
+-+
| 1969-12-20 11:13:20 |
+-+
On the FreeBSD system the same command returns:
mysql>
:
mysql> SELECT FROM_UNIXTIME(-100);
+-+
| FROM_UNIXTIME(-100) |
+-+
| 1969-12-20 11:13:20 |
+-+
On the FreeBSD system the same command returns:
mysql> SELECT FROM_UNIXTIME(-1
Hi, Peter!
* Peter Valdemar M?rch <[EMAIL PROTECTED]> [04/12/28 17:33]:
> Hi there,
>
> A bug was fixed in 4.0.23:
> >* Fixed bug which caused FROM_UNIXTIME() function to return wrong
> > result if the argument was too big.
> >http://bugs.mysql.com/6439
&
Hi there,
A bug was fixed in 4.0.23:
* Fixed bug which caused FROM_UNIXTIME() function to return wrong
result if the argument was too big.
http://bugs.mysql.com/6439
However, it looks like it has side effects:
select FROM_UNIXTIME(0) returns "1970-01-01 01:00:00" in 4.0.22 bu
Thank you Michael for your very thoughtful reply. I know that it takes
time and effort to answer at the level you did.
Michael Stassen Michael.Stassen-at-verizon.net |Lists| wrote:
> You seem to have a fundamental misunderstanding of the TIMESTAMP type.
> No timezone or DST information is stored
st or second occurrence of that time. No system could -- additional
info is required.
It seems that internally MySQL stores timestamp values with all
timezone and DST/non-DST information intact. But all operations (e.g.
TIMEDIFF(), FROM_UNIXTIME() and UPDATE TABLE SET
timestamp=timestamp+0) d
seems to be that "October 31, 2:15 am" is
ambiguous and MySQL cannot disambiguate between them.
It seems that internally MySQL stores timestamp values with all timezone
and DST/non-DST information intact. But all operations (e.g. TIMEDIFF(),
FROM_UNIXTIME() and UPDATE TABLE SET timestam
ambiguous and MySQL cannot disambiguate between them.
It seems that internally MySQL stores timestamp values with all timezone
and DST/non-DST information intact. But all operations (e.g. TIMEDIFF(),
FROM_UNIXTIME() and UPDATE TABLE SET timestamp=timestamp+0) destroy this
important information and o
Joseph Bueno <[EMAIL PROTECTED]> написа :
> [EMAIL PROTECTED]
> wrote:
> > Hello,
> > i build one query in my mysql:
> > mysql> select timestamp from lastauth where month(from_unixtime(timestamp) =
> 6);
> > Empty set (0.00 sec)
>
[EMAIL PROTECTED] wrote:
Hello,
i build one query in my mysql:
mysql> select timestamp from lastauth where month(from_unixtime(timestamp) = 6);
Empty set (0.00 sec)
Query is empty, but:
my timestamp table:
++
| timestamp |
++
| 1056981323 |
++
1 row in
Hello,
i build one query in my mysql:
mysql> select timestamp from lastauth where month(from_unixtime(timestamp) = 6);
Empty set (0.00 sec)
Query is empty, but:
my timestamp table:
++
| timestamp |
++
| 1056981323 |
++
1 row in set (0.00 sec)
mysql>
>Description:
On a windows or linux system where the time is set to local time, the
function from_unixtime incorrectly applies the offset from UTC to Local to
the result. For example when set to EST, "select from_unixtime(0);"
returns "1969-12-31 19:00:00". In fact, sec
While trying to fix my previous database problem, I discovered that
FROM_UNIXTIME
does not function as I expected (or MySQL can't do math). This is 3.23.38
(upgrading
to 3.23.40 in the next few days):
SELECT UNIX_TIMESTAMP(End_Time) - (Hours * 60 * 60) from Projec
14 matches
Mail list logo
