Re: [fw-db] ZendFramework Application vs TestCase Connection

I just wanted to follow up on this thread to confirm that the below fix indeed is the antidote to PHPUnit (bundled with Zend Studio) not connecting properly for unit tests. Thanks Till and Luiz for helping me get to the bottom of this!

-Mike

On Fri, Jan 16, 2009 at 6:40 PM, Mike Bronner <mike.bronner@gmail.com> wrote:

Hi Till, while you have been reviewing this (and thanks so much for your support and encouragement), I have been keeping at it. I found something that appears to have moved me in the right direction:
Zend Studio had PHP CGI as the default run-time. I changed the default to PHP CLI, and everything is working as a charm. I think somewhere the project I am working on must have been configured to run against the CLI version (which uses up-to-date libraries), while the CGI version uses the outdated stuff.

At any rate, I am now able to connect and am receiving bonnefied SQL errors that are due to me, and not my environment. :)

I'll report back once I can confirm for sure.

Thanks!
Mike

On Fri, Jan 16, 2009 at 6:19 PM, till <klimpong@gmail.com> wrote:

On Sat, Jan 17, 2009 at 2:21 AM, Mike Bronner <mike.bronner@gmail.com> wrote:
> Sure, thanks for following up, Till.
>
> Let me check if I can share the phpinfo() output of each.
> I am indeed able to load the MYSQL drivers, but for some reason it's loading
> an insanely old version of the client API (3.x). I believe the latest
> versions are somewhere in the 5.x range? At any rate, the problem now has
> migrated to "Client does not support authenticated protocol requested by
> server; consider upgrading MySQL client."
> Google'ing this has resulted in advice on how to circumvent the error using
> MYSQL's OLD_PASSWORD command (or similar), or install updated clients.
> However, using the OLD_PASSWORD command is not an option, and I am unsure as
> how to update the mysql client (I copied over the latest MYSQL*.so files,
> and that didn't seem to help).
>
> I guess the main thing that is frustrating here is that at the core this
> appears to be a Zend Studio issue. I don't think I should be going through
> all these hoops to make PHPUnit jive with Zend Studio when it already came
> bundled with it; hence my question if I should be asking this elsewhere (I
> did in fact go ahead and post this in the Zend Studio support forum to see
> if there has been any experience with this there as well).
>
> I have attached the two phpinfo() results. The PHPUnit output is
> "phpinfo_not_working.html".

Cool, ok, so the phpinfo_not_working is clearly compiled against MySQL
3.x (scary) which breaks the test when you try to connect with a 3.x
client (your mysql/php) to a 4.x server.

If that is an issue of your environment or Zend Studio -- I'm not
entitled to say that. I'm guessing it's Zend Studio because the other
phpinfo looks fitter in this regard. ;-) While MySQL 3.x EOL'd a while
ago, there were some initial issues with migrating to 4.x because of
the license (I don't recall it all) maybe that's why they are stuck?

For the sake of completeness it would be nice if you update the thread
so Google picks it up and helps someone else -- if you manage to
resolve the issue.

In the meantime, I suggest you install PEAR and phpunit yourself. If
you need help, there are a lot of people on IRC (e.g. #pear @ efnet)
to help you out.

Till

--
Celebrate Liberty, Freedom, and Rights at http://www.theconstitutionalist.us.

--
Celebrate Liberty, Freedom, and Rights at http://www.theconstitutionalist.us.