CID Superfecta cache in some cases expires entries prematurely

Given DIDs D1 and D2 and Superfecta schemes S1 and S2, where S1 is used for D1 and S2 is used for D2. Both S1 and S2 use Superfecta Cache, S1 with a cache timeout of 2 days and S2 with a cache timeout of 7 days. The Mysql cache database is shared by all instances of Superfecta Cache.

Then:

1. Perform a lookup using S2; result is cached
This deletes all cache entries older than 7 days
2. 3 days later, perform a lookup using S1; result is cached
This deletes all cache entries older than 2 days
3. The entry cached in Step 1, with a 7-day timeout, is now gone, 4 days prematurely

Workaround: Use the same cache timeout for all Superfecta schemes that use Superfecta Cache.