maria-developers team mailing list archive

[Henrik Ingo <henrik.ingo@xxxxxxxxxxxxx>]

On Tue, Sep 22, 2009 at 10:42 AM, Kristian Nielsen
<knielsen@xxxxxxxxxxxxxxx> wrote:
> Henrik Ingo <henrik.ingo@xxxxxxxxxxxxx> writes:
>
>> Where else would @@TIMESTAMP be modified? Can a user do that from SQL?
>
> Yes (or @TIMESTAMP at least)..
>
>    mysql> set TIMESTAMP=100;
>    Query OK, 0 rows affected (0.00 sec)
>
>    mysql> select now();
>    +---------------------+
>    | now()               |
>    +---------------------+
>    | 1970-01-01 01:01:40 |
>    +---------------------+
>    1 row in set (0.00 sec)
>
>    mysql> show full processlist;
>    +----+------+-----------+------+---------+------------+-------+-----------------------+
>    | Id | User | Host      | db   | Command | Time       | State | Info                  |
>    +----+------+-----------+------+---------+------------+-------+-----------------------+
>    | 15 | root | localhost | test | Query   | 1253605187 | NULL  | show full processlist |
>    +----+------+-----------+------+---------+------------+-------+-----------------------+
>    1 row in set (0.00 sec)
>
>> (If so, why???)
>
> Loading mysqlbinlog output, testing, ... and confusing
> SHOW FULL PROCESSLIST :-)
>

Ok, now I remember the point why you use it. (essentially, any
re-inserting of old data where timestamp columns are involved.)

So if you are arguing that SHOW FULL PROCESSLIST current behavior is a
bug, then you might be right?

henrik
-- 
email: henrik.ingo@xxxxxxxxxxxxx
tel:   +358-40-5697354
www:   www.avoinelama.fi/~hingo
book:  www.openlife.cc