(dev/core#217) PrevNext - Probe for best available implementation (memory-backed...
authorTim Otten <totten@civicrm.org>
Mon, 9 Jul 2018 00:54:07 +0000 (17:54 -0700)
committerTim Otten <totten@civicrm.org>
Tue, 24 Jul 2018 01:19:53 +0000 (18:19 -0700)
commit9909834979269b136c4a65be9af9dfdc158ccfee
tree20ff12fa021161130503def30bc076d174a0a41a
parent8148791114a53750ec080191b391336077e68965
(dev/core#217) PrevNext - Probe for best available implementation (memory-backed or SQL-backed)

Before
------

The `prevnext` service is always an instance of `CRM_Core_PrevNextCache_Sql`.

After
-----

If you define `CIVICRM_DB_CACHE_CLASS`, and if there's a corresponding
service `prevnext.driver.{mydriver}`, then it will use that service.

Otherwise, it will use `prevnext.driver.sql` (`CRM_Core_PrevNextCache_Sql`).
Civi/Core/Container.php