>>You can learn that you don't have a problem with globals that are in the >>current script's name space and not declared explicitly in any package. >>You may still have problems with globals in other packages, or closures. > >This, as well as http://groups.yahoo.com/group/modperl/message/57338, >proved very helpful. I did some rather quick editing to match this >"Singleton pattern", and I've yet to be duplicate the caching that >was happening. I'm stilling having trouble with the missing-but- >existing function call [1], but I'll be able to poke around with >a little more understanding before I bug you again <g>.
Alrighty. I've yet to figure out what my ->connect problem [1] is. All my settings caching problems have been fixed, as I've yet to duplicate the issue in about 300 to 400 loads. Anywhere I should look? What I know:
* LibDB::DB is correctly determining the database type.
* LibDB::DB is correctly returning a blessed class for that database type (LibDB::DB::MySQL).
* LibDB::DB::MySQL->connect does exist.
* LibDB::DB::MySQL->connect does work.
But, still, I'll randomly get the error [1]. From ignorance, this *can't* be related to globals or caching, right (since it is reporting the correct package name, and a cache wouldn't suddenly "remove" a function)? What should I look for?
[1] http://groups.yahoo.com/group/modperl/message/57303 Program fragment delivered error ``Can't locate object method "connect" via package "LibDB::DB::MySQL".
-- Morbus Iff ( i put the demon back in codemonkey ) Culture: http://www.disobey.com/ and http://www.gamegrene.com/ Spidering Hacks: http://amazon.com/exec/obidos/ASIN/0596005776/disobeycom icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
