Just a note. With Justin's example, the SELECT *does* issue a warning in
MariaDB 10. The same SELECT on an empty table returns a warning only on MySQL
5.6, not on MariaDB 10. IMO, the user
should be aware that his program is buggy, no matter if the table is
empty or not.
Federico__
Hi,
How interesting.
This behavior yields some strange results:
Database changed
mysql> CREATE TABLE t (c TIMESTAMP) ENGINE=InnoDB;
Query OK, 0 rows affected (0.06 sec)
mysql> insert into t values (1);
Query OK, 1 row affected, 1 warning (0.03 sec)
mysql> show warnings;
+-+--+
Hi, Justin!
On Dec 11, Justin Swanhart wrote:
> I disagree about as vehemently as possible. You should get a warning on
> comparisons between incompatible types that cause float conversions. You
> get unexpected wrong results otherwise. The MySQL warning is therefor
> critical.
That would be t
Hi,
1) There's no master and no slave, there's a totally different thing:
Primary Component. It is the part of the cluster that is allowed to
modify data. So you either start a new cluster or join a node to the
primary component. If you join a node to a non-primary component, then
it is in no
I disagree about as vehemently as possible. You should get a warning on
comparisons between incompatible types that cause float conversions. You
get unexpected wrong results otherwise. The MySQL warning is therefor
critical.
Not warning for this is just as stupid as not having ONLY_FULL_GROUP_B
hum, must check but i think that galera cluster is 3+ nodes, i only
tested with 3+ here, didn't tested with 2 nodes yet
2013/12/11 AskMonty KB :
> Hello,
>
> A new question has been asked in "MariaDB FAQ" by maximilianodipietro:
>
> Hi people, i have a two nodes cl
Hello,
A new question has been asked in "MariaDB FAQ" by maximilianodipietro:
Hi people, i have a two nodes cluster of MariaDb, and i need some help, i have
this simple script to do a solve failover, the script works like this: if the
master node dies, the script
Hi, Federico!
On Dec 11, Federico Razzoli wrote:
> Hi! MySQL 5.6 returns a warning for wrong datatypes, with any SQL_MODE:
>
> mysql> CREATE TABLE t (c TIMESTAMP) ENGINE=InnoDB;
> Query OK, 0 rows affected (0,31 sec)
>
> mysql> SELECT c FROM t WHERE c = 1;
> Empty set, 1 warning (0,00 sec)
> Wa
Hi! MySQL 5.6 returns a warning for wrong datatypes, with any SQL_MODE:
mysql> CREATE TABLE t (c TIMESTAMP) ENGINE=InnoDB;
Query OK, 0 rows affected (0,31 sec)
mysql> SELECT c FROM t WHERE c = 1;
Empty set, 1 warning (0,00 sec)
Warning (Code 1292): Incorrect datetime value: '1' for column 'c' a
9 matches
Mail list logo
