On Tue, Dec 07, 2004 at 11:13:01AM +0000, Nicholas Clark wrote: > On Mon, Dec 06, 2004 at 07:53:01PM -0500, Matthew Persico wrote: > > > At the top of this thread and at various other entries, the point is > > made that many times, the parameters for connection are pulled from a > > source that has them listed individually. Why make the > > The other point, possibly more fundamental, was that various DBD drivers > with similar concepts (host, port, DB name) have vastly dissimilar ways > of naming them, and of joining them together into DBD strings, which is > very confusing. Soooooo, you know that your bolts and nuts are imperial > rather than metric, but were they Whitworth, BSF, UNC or something else?
Exactly. Which is why I said... --- The simplest fix is to standardize one set of driver DSN attribute names so that at least the host, port, and database (schema) can be specified in a portable way. Most drivers already support the "foo=bar;..." style in the DSN string. They'd just need to support alternative names for some attributes. As for what names to use, "host" and "port" are easy choices. For the database there's "db", "dbname", and "database". I'd probably go with "db". --- So now what all you zelots out there need to do is (gently) nag the authors of your favorite drivers to implement this change. The most gentle and effective way of doing that is to send them a patch. Tim.
