Comment 3 for bug 1861099

php-horde-db is a library used for database access by Horde applications. The source package generates only a binary package of the same name. Nothing Build-Depends on php-horde-db. All binary packages currently in focal-proposed are generated from the following (29) source packages:

php-horde
php-horde-activesync
php-horde-alarm
php-horde-ansel
php-horde-auth
php-horde-cache
php-horde-content
php-horde-core
php-horde-gollem
php-horde-group
php-horde-history
php-horde-imap-client
php-horde-kronolith
php-horde-lock
php-horde-mnemo
php-horde-nag
php-horde-passwd
php-horde-perms
php-horde-prefs
php-horde-rdo
php-horde-sesha
php-horde-sessionhandler
php-horde-share
php-horde-token
php-horde-trean
php-horde-turba
php-horde-vfs
php-horde-whups
php-horde-wicked

I retrieved all of these and grepped for "getLimit" and found zero hits. Exploring lib/Horde/Db/Adapter/Base/Column.php and lib/Horde/Db/Adapter/Base/ColumnDefinition.php from src:php-horde-db, it seems that the parsing is _extractLimit, stored in a private member variable called _limit, and accessed only via public method getLimit.

I conclude that there do not appear to be any actual users of this API method inside Horde itself, then from the perspective of php-horde-db, while the test is correctly failing, the behaviour change in MySQL, as far as I can tell, will not affect Horde's behaviour. It therefore should be OK to disable or modify the test in php-horde-db for the purposes of the archive.

There may be other consumers outside the archive of php-horde-db's getLimit API, or of MySQL's behaviour directly, that remain affected.