I am in a serious trouble because of Alzabo::MethodMaker...
I hope I can be exhaustive and try to explain at the best
clarity level what has happened.
I have a site which is written in Mason, and relies upon
several databases in MySQL, which have different names but
hold tables with the same names (and same column names).
I need this layout because I am doing the same job from year
to year (I handle datas in a High School), thus naming my
databases with the years numbers (e.g.: 2002_2003
Having rewritten most of my code in order to make a
transition to Alzabo from the general DBI interface, I am
now realizing with a certain shock, that I cannot use the
namer sub coming from Apprentice, for example, in order to
create nice methods (tables ending in _t, columns in _c,
plurals for foreign keys and so on), since when I load my
Apache invoking different:
`use Alzabo::Method::Maker (schema=>'a',all=>1,etc)`
`use Alzabo::Method::Maker (schema=>'b',all=>1,etc)`
it complains about redefined subroutines (it finds the same
tables with the same column names), and then I can no longer
get to the right table, because only the 1st loaded one gets
accessed by my calls...
Of course, I am quite sure that I am loading the right
schema files, with a small package that I copied from
Apprentice::Data.pm, with a $Schema global.
What can I do? It would be a nightmare to write again all of
my code WITHOUT MethodMaker...
Any help would be greatly appreciated.
Thank in advance
Get latest updates about Open Source Projects, Conferences and News.