Support Forum
No two rows is not right and might be part of the problem. Remove one of the rows - doesn't matter which as long as for the one you leave the meta_type column is set to 'topic_cache' and the meta_key column is set to 'new'.
And on the second question then yes - that is the data needing removal.
YELLOW
SWORDFISH
|
Yes - as soon as you said two then it all fell into place.
You should still remove the redundant one. This will now be the one where the data you removed has stayed removed. The other will have repopulated.
So at some point a second cache record was created but, because we only expect one, the old one that was no longer being updated was being queried but oddly I bet the newer one was the one being updated.
The important question, of course, is why there were two. That is something I will have to look into to see if I can fathom a way that might come about.
YELLOW
SWORDFISH
|
Yellow Swordfish said
The important question, of course, is why there were two. That is something I will have to look into to see if I can fathom a way that might come about.
would the innodb conversion that I ran have any impact on that? Also I deleted 31, should I change the meta id of watches to 31 or just leave it 32?
you guys have been busy this morning!
Visit Cruise Talk Central and Mr Papa's World
1 Guest(s)