Sam Vilain wrote: > Maxim Sloyko wrote: > >> But this is not the point. The point was that usage of some file with >> passwords by *DEFAULT* is not the way to go, IMHO. It raises more >> problems than it solves. > > > Can you give an example of such a problem that wasn't already there? > > Just to be clear, the file would only need to contain passwords if the > DBD requires them. > > Sam.
> May be it is just me, but having a bunch of config files is not very > good. Config files should be for program, not for separate modules of > that program. They are hard to manage, when there are many of them. > Besides, DBI is a high level abstraction and it is not a good idea to > tie it to some file. May be it is better to let DBD:: modules choose? > For example, you can pass some parameter to the driver in connect > string, which tells it, where passwords are stored. Something like this > is impleneted in DBD::Oracle, where you can just pass 'sid' parameter to > the driver, the rest configuration parameters (except passwords and > usernames) are read from oracle config file, from the section to which > that sid parameter points. No, it is not just you. I find this type of setup appalling. As an Oracle DBA, I do not want yet another place where I will need to manage passwords. This type of setup will most likely restrict and possibly prohibit the use of Oracle OID and Enterprise User Management. It is, IMHO, unacceptable to force this type of behavior into a database access module and onto the general user community. > I don't mind if you implement this ".dbi" feature though, I just want it > to be invisible :) i.e. don't check this file, if I explicitly supply > username and password (this is obvious, right?) and show some warnings > if don't. Say, make a connect parameter "use_dot_dbi", which is zero by > default. > -- > Maxim Sloyko -- Ron Reidy Lead DBA Array BioPharma, Inc. This electronic message transmission is a PRIVATE communication which contains information which may be confidential or privileged. The information is intended to be for the use of the individual or entity named above. If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. Please notify the sender of the delivery error by replying to this message, or notify us by telephone (877-633-2436, ext. 0), and then delete it from your system.