Re: Re^n: DBX offers simplified access to the DBI

So to amplify a bit, what he's (probably) terming a symbolic reference, I think I'd call dynamic method selection, and it does, in fact, answer your concern.

Actually, that would raise a separate concern. Now, to protect myself against bogus stuff coming out of a config file, I have to wrap code in an eval block. And even then I'm not guaranteed that what comes out of the config file won't be the name of some method in DBX that I don't want to call.

Comment on Re: Re^n: DBX offers simplified access to the DBI Download Code

Replies are listed 'Best First'.
Re: Re: Re^n: DBX offers simplified access to the DBI by batkins (Chaplain) on Feb 19, 2003 at 11:38 UTC
Actually, the DBX package doesn't contain any methods. So you can ONLY use it to initiate a connection.	[reply]
Re^n: DBX offers simplified access to the DBI by adrianh (Chancellor) on Feb 19, 2003 at 14:09 UTC
What if somebody wants to subclass it and add their own methods? What if you change your mind at a later date and need to add some methods? What if somebody invents a database called `isa` or `can` (darn that UNIVERSAL class)? :-) Also, saying `DBI->connect` tells me exactly what is happening by it's name alone. Where ever I see it I known what is happening. With `DBX->mysql`, `DBX->oracle`, `DBX->Sybase`, etc - the same task (connecting to a database) looks different depending on the database being connected to. IMHO this makes the code harder to understand. Call me old fashioned - but I still go for the whole method names should be verbs meme:-)	[reply] [d/l] [select]