[dev] [PATCH] passwd sql & socket parameter

[Rob Lineweaver]

Quoting Chuck Hagenbuch <chuck at horde.org>:

> This is a bug in your configuration, not a bug in the driver.

True.  But if that's your answer then I don't understand the purpose of the five
existing lines seen in the patch.  They import the site's Horde config values
for all the other DB params (if not explicitly overridden in this backend), so
why should 'socket' be left out?  I would guess that 95% of the time a site
administrator is going to use the same method to connect to the database for
all the Horde apps, so why require them to always specify 'socket' in this
backend config?  I could leave out any of the other  parameters and it wouldn't
be a "bug" in my configuration because it would pull it from my main Horde sql
config.

If you really think the patch is inappropriate then I'll send another one that
adds 'socket' to the example sql config in passwd/config/backends.php.dist with
a comment so admins know they have to specify 'socket' explicitly in order to
avoid frustrating PEAR::DB errors.

Rob Lineweaver
Network Administrator
Harrisonburg City Public Schools