Re: Weird result set from PEAR's DB

On Tue, 29 Mar 2005 18:02:08 -0500, Matthew Weier O'Phinney <mweierophinney@gmail.com> wrote: > On Tue, 29 Mar 2005 14:52:14 -0800, Joe Stump <joe@joestump.net> wrote: > > The only thing differing between the two is one is PPC and the other is > > x86. I can reproduce the bug by copying and pasting the query into my > > x86 mysql terminal client as well. > > > > PPC: > > > > jstump@Joseph-Stumps-Computer > > enotes$ mysql --version > > mysql Ver 14.7 Distrib 4.1.10a, for apple-darwin7.7.0 (powerpc) > > jstump@Joseph-Stumps-Computer > > enotes$ uname -a > > Darwin Joseph-Stumps-Computer.local 7.8.0 Darwin Kernel Version 7.8.0: > > Wed Dec 22 14:26:17 PST 2004; root:xnu/xnu-517.11.1.obj~1/RELEASE_PPC > > Power Macintosh powerpc > > > > x86: > > > > noc@poweredge:~$ mysql --version > > mysql Ver 14.7 Distrib 4.1.7, for pc-linux (i686) > > noc@poweredge:~$ uname -a > > Linux poweredge 2.4.26-bf2.4 #1 SMP Wed May 26 08:34:11 PDT 2004 i686 > > GNU/Linux > > noc@poweredge:~$ > > > > Oddly enough, if I remove \n's from the query string it works fine: > > > > $sql = "SELECT * > > FROM users > > WHERE username='foo@example.com'"; > > > > to: > > > > $sql = "SELECT * FROM users WHERE username='foo@example.com'"; > > > > That fixes the problem as well as adding the DB name before the table > > (eg. users -> mydb.users). Very odd stuff here. > > What OS is the mysql server running on? This sounds like a classic case of > alternate line endings causing issues. You say "if I remove the \n's from the > query", but are you removing \n's, \r's, \r\n's, or what? > This is probably spot on. What computer are you editing this script on? If it's a mac, the line endings may be \r instead of \n. Perhaps this is what screws it up. Try changing your script to use unix line endings (\n). -- Justin Patrin