Re: Problem when deleting Class::DBI objects

Not an answer to your question, but just a remark: Did you consider using DBIX::Class instead of Class::DBI? I find DBIX::Class better documented and generally easier to use.

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

Comment on Re: Problem when deleting Class::DBI objects

Replies are listed 'Best First'.
Re^2: Problem when deleting Class::DBI objects by Hue-Bond (Priest) on Nov 28, 2007 at 13:35 UTC
Don't let `FOO::Indicators::PPO` inherit from `FOO::Indicators`, but make it a subclass of `Foo`. Thanks! That did it, but now I have a new question: what happens with the methods I had in `FOO::Indicators`? I tried moving them to `FOO` and it works but I guess there's a better solution. Did you consider using `DBIX::Class` instead of `Class::DBI`? The truth is that I didn't. I found `Class::DBI` when searching for something, and then I didn't know that there were more modules available for that. Maybe in a future rewrite... -- David Serrano	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^2: Problem when deleting Class::DBI objects
by Hue-Bond (Priest) on Nov 28, 2007 at 13:35 UTC

Don't let FOO::Indicators::PPO inherit from FOO::Indicators, but make it a subclass of Foo.

Thanks! That did it, but now I have a new question: what happens with the methods I had in FOO::Indicators? I tried moving them to FOO and it works but I guess there's a better solution.

Did you consider using DBIX::Class instead of Class::DBI?

The truth is that I didn't. I found Class::DBI when searching for something, and then I didn't know that there were more modules available for that. Maybe in a future rewrite...

--
David Serrano

[reply]
[d/l]
[select]