Bug #3465

Flexibility in location of modules/drivers, etc.

Details

Request #3465	Flexibility in location of modules/drivers, etc.
Submitted	2005-02-14 17:08 UTC
From	ceefour at gauldong dot net
Status	Closed
Package	MDB2
PHP Version	5.0.3
OS	Linux, Apache 1.3.33
Roadmaps	(Not assigned)

Comments

[2005-02-14 17:08 UTC] ceefour at gauldong dot net

Description:
------------
The first thing I did was to avoid putting any of my "proprietary" (i.e.
drivers not bundled with MDB2) files outside of the MDB2 directory. It
seems that this is impossible, eh? The same problem also happens to MDB2
modules (loaded by loadModule). So I think it'd be great if MDB2
autodetected if an expected class already exists then it is not necessary
to include the driver/module file. This will make MDB2 not require the
drivers/modules to always reside in MDB2 directory, as I can include the
driver/module file first (wherever they may be), then call
connect/loadModule and it will use the class that's already loaded.
Please, don't break my heart on this one.

Well, it turned out I had to mess with MDB2 directories. OK, no problem. I
hope I don't accidentally delete my files when I upgrade MDB2 in the
future. That'll definitely make me cry.

[2005-02-22 09:37 UTC] smith at backendmedia dot com

This bug has been fixed in CVS.

In case this was a documentation problem, the fix will show up at the
end of next Sunday (CET) on pear.php.net.

In case this was a pear.php.net website problem, the change will show
up on the website in short time.

Thank you for the report, and for helping us make PEAR better.

I have fixed this in CVS. One other solution is to use add another include path before the PEAR include path.