Bug #1549 Strange behaviour of 4.1.1 current (12 Oct 2003)

• Submitted: 14 Oct 2003 9:26
• Modified: 14 Oct 2003 12:09
• Reporter: Vadim S
• Status: Duplicate
• Category: MySQL Server
• Severity: S1 (Critical)
• Version: 4.1.1 current (12 Oct 2003)
• OS: Linux (Linux)
• CPU Architecture: Any

[14 Oct 2003 9:26] Vadim S

Description:
gcc 3.3.1, libc 2.3.1, Linux Slackware
OK, using 4.0.15a.
everything work, nice.
installing 4.1.1 current.
everything works, OK.
the day after:
using selects like
select * from table where Auth_id=100 and (a=10 or b=20) order by ID;
produces nothing, query like:
select COUNT(*) from table where Auth_id=100 and (a=10 or b=20);
produces normal number that is greater than 0.

How to repeat:
mysql> select * from msg where Author=6213 and (Saved='s' or Saved='n') order by ID;
Empty set (0.00 sec)

mysql> select COUNT(*) from msg where Author=6213 and (Saved='s' or Saved='n') order by ID;
+----------+
| COUNT(*) |
+----------+
|      191 |
+----------+
1 row in set (0.01 sec)

mysql> select ID from msg where Author=6213  order by ID;
......
| 18540 |
+-------+
220 rows in set (0.01 sec)

-------------------------------------------
table is like:
CREATE TABLE msg (
  ID int(11) unsigned NOT NULL auto_increment,
  Title varchar(250) default NULL,
  Updated timestamp NOT NULL,
  Author int(11) unsigned NOT NULL default '0',
  Saved enum('n','r','s','rs') NOT NULL default 'n',
  Entered_date timestamp NOT NULL,
  Read_ enum('n','r','s','rs') NOT NULL default 'n',
  Sent enum('n','s','i') NOT NULL default 'n',
  PRIMARY KEY  (ID),
  KEY index_0 (Author),
  KEY index_7 (Author,Saved)
) TYPE=MyISAM;

[14 Oct 2003 9:33] Vadim S

Situation on the first day was normal.
the day after, I saw the situation described.
OK. stop the daemon. restart it. bug remains.
Options used for compilation:
./configure --prefix=/usr/local/mysql \
--enable-thread-safe-client --with-readline \
--with-innodb --with-berkeley-db --with-openssl --with-charset=koi8r \
--with-vio --enable-local-infile --enable-assembler

[14 Oct 2003 12:09] Alexander Keremidarski

This the case from Bug report #1549

Please follow same bug when sending more details.