hmm,
the idea is to have the actual methods and whatever way you store and fetch stuff plugable, so, down the line I can say,
my $scheme = 'FooSQL'; my $h = TheDb->new($scheme);
And, perhaps someone else, with a different setup and wants will go:
my $scheme = 'DB_File'; my $h = TheDb->new($scheme);
having all the subclasses loaded at the same time would be incredibly wasteful and useless, since I may not know exactly what DB (or subclass module) is there.
This may seem like more work, why would you have n ways of doing the same thing? Well, you may not have a Spiffy SQL and are OK with using a plaintext solution, knowing some performance woes.
This is for a very mature, stable app, not a quick 15 minute script.
-justin simoni
!skazat!
In reply to Re: Re: Loading a different Module depending on the Configuration
by skazat
in thread Loading a different Module depending on the Configuration
by skazat
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |