[Maypole] Maypole startup sequence

[Peter Speltz]

oops. forgot to post to list

--- Dave Howorth <dhoworth@mrc-lmb.cam.ac.uk> wrote:

> Peter Speltz wrote:
> > That's awesome. Thanks. One question i have about in the
> > "Class::DBI::Loader::mysql::_load_classes" part. Where it says " After
> that, it
> > pushes Class::DBI::mysql on to the inheritance list of the class and calls
> > set_db()  . .. " I notice it "pushes" it on ISA list.
> 
> Yeah, I think that's wrong.
> 
> > Later on in setup Maypole
> > iterates and makes each class inherit from Maypole->model.  Somehow in this
> > scheme,  Class::DBI ends up earlier in the ISA list than Class::DBI::mysql
> for
> > me because Class::DBI methods are used before Class::DBI::mysql methods of
> same
> > name.  Any ideas on why that is or if that is a bug?
> 
> I was just looking at this myself (that's what prompted me to post the 
> doc :) because I'd just noticed the same thing. In my app, Class::DBI's 
> deprecated column_type method is getting called in preference to 
> Class::DBI::mysql's real one. But in my app, I've tweaked the model and 
> replaced the loader so I have to dig a lot to be sure whether it's 
> something I've done or not. 

I can tell you i had the exact same problem and encountered it the same way. 
So its a loader thing. I use the standard Maypole way to load , whatever that
is :). To fix it i just made Maypole::Model::CDBI use Class::DBI::mysql as it's
base.  Thanks for taking the time to dig through that and figure it out.





> 


=====
pjs

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com