in reply to Re: A Growing Dislike for SQL-OOP Mappers
in thread A Growing Dislike for SQL-OOP Mappers
When I don't like the Class::DBI methods, I make my own.
My complaint was that sometimes that's just not possible if the SUPER classes internals call the method you are overriding (as apposed to it's version of that method). I only want the consumer of my class to call my new; not the the internals of the superclass; yet I still want all of the is-a relationship perks; column and setup accessors.
Updated...
For example, create a class that is-a Class::DBI and override create. Now call find_or_create(). Bad things happen.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^3: A Growing Dislike for SQL-OOP Mappers
by itub (Priest) on Aug 22, 2005 at 20:39 UTC | |
by jk2addict (Chaplain) on Aug 22, 2005 at 21:33 UTC | |
by perrin (Chancellor) on Aug 22, 2005 at 23:16 UTC | |
by TimToady (Parson) on Aug 23, 2005 at 00:11 UTC | |
by itub (Priest) on Aug 22, 2005 at 22:28 UTC |