Henrik Ingo henrik.i...@avoinelama.fi 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()
On Tue, Sep 22, 2009 at 10:42 AM, Kristian Nielsen
kniel...@knielsen-hq.org wrote:
Henrik Ingo henrik.i...@avoinelama.fi 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
Henrik Ingo henrik.i...@avoinelama.fi writes:
I'm the wrong person to answer, but seems to me we should at this
stage prefer being bug-for-bug compatible and changing semantics
between MariaDB and MySQL may turn out to be more of a problem than
being helpful. (If we could agree with the MySQL
On Mon, Sep 21, 2009 at 2:23 PM, Kristian Nielsen
kniel...@knielsen-hq.org wrote:
Henrik Ingo henrik.i...@avoinelama.fi writes:
I'm the wrong person to answer, but seems to me we should at this
Just wanted to leave that quote :-)
I re-read your original text and offer some other non-expert
On Fri, Sep 18, 2009 at 1:55 PM, Kristian Nielsen
kniel...@knielsen-hq.org wrote:
There is a replication FAQ, which says this:
http://dev.mysql.com/doc/refman/5.1/en/replication-faq.html
16.3.4.3: How do I know how late a slave is compared to the master?
You can read the
Hi,
While merging the Percona microsec_process patch (the 5.1 port of the patch is
called acc-pslist), I encountered a problem related to Bug#22047:
http://bugs.mysql.com/bug.php?id=22047
The issue is with the exact behaviour of the TIME column of SHOW FULL
PROCESSLIST and
6 matches
Mail list logo
