Tickets :: Comment on [#9342] using an index on horde

* Your Email Address
* Spam protection	Enter the letters below: . ,.___. ..__ . . \./ _/ \|[__)\|\/\| \| ./__.\__\|[__)\| \|
Comment	> In H5, horde_cache defines cache_id as an autoincrement key. This > (should?) automatically marks this field as a primary key. (Testing > on postgresql, attempting to alter the table and add cache_id causes > a "multiple primary keys for table not allowed" error). > > And I don't see how adding a unique index on cache_id and timestamp > helps us. We don't need to enforce the combo of those two fields to > be unique. And indexing on cache_id should be sufficient - SQL > server should quickly look up cache_id, and then can quickly compare > the timestamp field. > > In other words, I think our cache table is already sufficiently optimized.
Attachment
Watch this ticket