Hi all,
I'm seeing some rather wierd behavior in an update statement.
I'm running "Distrib 3.23.5-alpha, for pc-linux-gnu on i586" on
Slackware 3.4 with kernel 2.0.34
I upgraded MySQL around 21-dec-99 to 3.23.5 and i seems this
problem started sometime durring 26-dec-99.
The really wierd thing is that another identical database on
the same server have't had this update problem. This other
base is beeing accessed by a remote 3.22.x mysql (shell client).
Could it be a bug in the 3.23.5 client ???
My problem is showing the following sympthoms:
mysql> select count(*) from transfer where yymmdd=0;
+----------+
| count(*) |
+----------+
| 1167765 |
+----------+
1 row in set (15.69 sec)
mysql> select distinct (yy*10000)+(mm*100)+dd as yymmdd from transfer where yymmdd=0
> limit 20;
+----------+
| yymmdd |
+----------+
| 19991226 |
| 19991229 |
| 19991227 |
| 19991228 |
| 19991230 |
| 19991231 |
| 20000101 |
| 20000102 |
| 20000103 |
| 20000104 |
| 20000105 |
| 20000107 |
| 20000108 |
| 20000109 |
| 20000110 |
| 20000111 |
| 20000112 |
| 20000113 |
| 20000114 |
| 20000115 |
+----------+
20 rows in set (1 min 18.01 sec)
mysql> update transfer set yymmdd=(yy*10000)+(mm*100)+dd where yymmdd=0;
Query OK, 0 rows affected (48.76 sec)
Rows matched: 0 Changed: 0 Warnings: 0
mysql> select count(*) from transfer where yymmdd=0;
+----------+
| count(*) |
+----------+
| 1167765 |
+----------+
1 row in set (15.69 sec)
--
Later
Mogens Melander mailto:mogens@stripped
http://www.fumlersoft.dk http://www.trader.dk
http://www.birkerod.dk http://tux.trader.dk
