Re: Error using PEAR on Mac OS X
| From: | Ryan King | Date: | Wed, 16 Mar 2005 19:58:55 +0000 |
| Subject: | Re: Error using PEAR on Mac OS X | ||
| References: | 1 2 3 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-18090@lists.php.net to get a copy of this message | ||
On Mar 16, 2005, at 11:31 AM, Markus Arike wrote:
I'm happy to say that, I have been able to solve the PEAR problem that I was having. By accident, really. Seems that if I try to load a script with a PEAR include in it from my Apache Root web directory, the Sites directory, the scripts fail. But I made a new directory inside the Sites directory, and when I run the same scripts from there, they work!!! I am very happy that this mystery is finally solved. Not sure why they don't work from the root directory, maybe one of you nice gentlemen have a better idea (probably has something to do with permissions, but not sure).There's also the possiblity that you had a file in that path with the same name as the PEAR one you were trying to include (like 'DB.php'). Usually include paths have '.' as their first option.
Anyway, I off to re-write some of my mysql & mysqli scripts using the PEAR extension, and also see how easy it is to convert them to work with PostgreSQL. I assume portability is one of the main advantages of using the PEAR DB class.Of course, there many issues on DB portability- if that's really your ideal, MDB might be a better choice than DB, since DB only really abstracts the interface, not the datatypes. -ryan