RE: SELECT from network client vs. SELECT on the database server

How-To-Repeat:

1) Install mysql-3.23.53 on sun4u architecture Solaris 8

2) Install PERL 5.6.1 DBI 1.21 DBD::mysqlPP v0.03
on a separate machine, also sun4u Solaris 8

3) Use PERL DBI API on client (2) to connect to database
server (1).

If this is not a known bug, we may be willing to share
applicable portions of the database to recreate.

-----Original Message-----
From: bugs@lists.mysql.com [mailto:bugs@lists.mysql.com]
Sent: Friday, March 14, 2003 3:42 PM
To: Jason McCabe
Subject: Re: SELECT from network client vs. SELECT on the database
server


Your message cannot be posted to bugs@lists.mysql.com because it did not
follow the format expected by our spam/off-topic filter. To this list we
accept only repeatable bugs reports, meaning that you can describe a
set of steps we can follow to repeat the bug on our systems.

[snip]

If you are able to describe how we can repeat the problem, include the
string
"How-To-Repeat:" in the body of your message, followed by the detailed
description of what we need to do to make it happen, and our filter will
accept your message. If you use mysqlbug script, which comes with the MySQL
distribution, to post the message, it will be automatically accepted.

You have written the following:

---start of your message----
Hi.

I have strange one.

We're running mysql-3.23.53 on Solaris (2.)8 sun4u
architecture. Something has happened in our database
in that now a particular SELECT statement from a
network client (also Solaris 8 sun4u via PERL 5.6.1
DBI 1.21 DBD::mysqlPP v0.03) does not yield exactly
the same results that the EXACT same SELECT statement
returns if invoked directly from the MYSQL "shell" on
the database server. In particular, certain rows are
not returned in the networked invocation. However,
if an "ORDER BY" clause is added to the networked
version of the SELECT, it works fine. Weird.
We are not performing any kind of active replication.

I would point out that we performed power work in
our server room quite recently, and this anomaly has
shown up only since then. However, we shut down the
database and the server cleanly before the power work.

Any ideas?

Jason McCabe

---end of your message-------

MySQL Development Team


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread13965@lists.mysql.com
To unsubscribe, e-mail