fix(db): stringify scalar values in PDO blob serialization

[TDannhauer]

Summary

• Fix PDO BLOB serialization so scalar values (integers, floats, booleans) are stored correctly instead of empty binary data
• Apply the same change in both autoload trees: legacy lib/ (PSR-0) and modern src/ (PSR-4)
• Complements horde/prefs SQL storage fix; protects all callers of insertBlob() / updateBlob(), not only preferences

Problem

Horde_Db_Adapter_Pdo_Base and Horde\Db\Adapter\Pdo\Base extract LOB payload via _lobValueString() / lobValueString():

return is_string($data) ? $data : '';

Non-string scalars (e.g. integer 1 from checkbox preferences) are treated as invalid and serialized as an empty string. The database write succeeds, but the stored blob is empty.

This affected horde_prefs when integer values reached the DB layer without prior string coercion—for example IMP use_trash appeared saved in the UI but reloaded as disabled.

Solution

Stringify scalar LOB values before binding:

return is_string($data) ? $data : (is_scalar($data) ? (string) $data : '');

Changed files

Tree	File	Method
lib/ (PSR-0)	lib/Horde/Db/Adapter/Pdo/Base.php	_lobValueString()
src/ (PSR-4)	src/Adapter/Pdo/Base.php	lobValueString()

Both copies must stay in sync: horde/db autoloads Horde_Db_* from lib/ today and Horde\Db\* from src/ for the ongoing namespace migration.

Related change

• horde/prefs: lib/Horde/Prefs/Storage/Sql.php also casts preference values with strval() before wrapping them in Horde_Db_Value_Binary (defense in depth at the prefs layer)

Test plan

• Store integer 1 via Horde_Db_Value_Binary + updateBlob() on PostgreSQL; confirm pref_value / blob column is not empty
• Store integer 0 and string '1' / '0'; confirm round-trip matches input
• Save IMP checkbox preference use_trash and verify persistence without the prefs-only workaround
• Run existing horde/db unit/integration tests if available
• Smoke-test other BLOB writes (e.g. binary attachment metadata) to ensure no regression for stream/resource LOB values

[ralflang]

Do you see this across PDO or only on postgres?

[TDannhauer]

yes, affects all, as it is located in the base. added testcase with SQLite