Forum Discussion
Thought I'd check in to see if Cox leadership, supervisors, moderators and the vendor are doing everything possible to restore your posts. Nope. F. A. I. L.
Yea, I thought a Supervisor/Manager I met on Reddit was going to post or DM me some info but they have gone missing. Sorry for the false alarm.
- WiderMouthOpen3 years agoEsteemed Contributor
FYI: I sent another email asking for a update. Nothing so far.
- TiffanyR3 years agoFormer ModeratorHello WiderMouthOpen,
Thank you so much for your patience. I understand that this has been going on for a while and that can be frustrating. Our leadership team is still working with our Forum Provider to find a resolution. We will let you know as soon as we have an update.
Tiffany R.
Cox Support Forum Moderator- CurtB3 years agoHonored Contributor
@TiffanyR, For this discussion, assume a forum database with a "User" table of forum users and a "Reply" table of questions and discussions. Also, assume a unique User.UserID field and a Reply.CreatedBy field set to User.UserID of the forum user who created the Reply record.
... User Join Reply on User.UserID = Reply.CreatedBy...
Two months ago, WiderMouthOpen experienced an error while logging in, that I suspect corrupted his User record. That could have caused a new User record to be created with a different User.UserID value than the Reply.CreatedBy value of Reply records he created before the error (pre-error); breaking the join between them. The display query doesn't include Reply records without a matching User.UserID. In normal operation, Reply records are probably deleted during the delete User process. But Reply records orphaned by an unexpected event might still exist.
Determine if his pre-error Reply records are still in the database.
<previous User.UserID> could be obtained from a pre-error User table backup.
SELECT * FROM Reply WHERE Reply.CreatedBy = <previous User.UserID>;
If records are found, that would confirm my theory. The fix would be:
UPDATE Reply
SET Reply.CreatedBy = <current User.UserID>
WHERE Reply.CreatedBy = <previous User.UserID>;That should re-establish the join between his User and pre-error Reply records.
Two months without a fix is not good. Your provider's IT department needs to wash their hands so they don't get boogers on the keyboard.
Related Content
- 2 years ago
- 11 months ago
- 2 months ago
- 12 years ago