Re: Missing messages

Hi Tom:

I don't know of any issues with missing message links in postgres.  I
would be interested in your test script. I can run it against
issues.roundup-tracker.org or with permision against bugs python.org.

In message <CO3PR08MB7957E4C1DEF5F86C1C11CDE9CA149@CO3PR08MB7957.namprd08.prod.
outlook.com>,
Tom Ekberg writes:
>Investigating this further, I ran this query
>
>uw_chemistry=# SELECT * FROM msg__journal WHERE params LIKE '%476%';
>nodeid |          date           | tag | action |            params
>--------+-------------------------+-----+--------+------------------------------
>   1514 | 2017-12-07 16:10:20.203 | 33  | link   | ('issue', '476', 'messages')
>   1514 | 2017-12-12 22:55:13.576 | 33  | unlink | ('issue', '476', 'messages')
>   1515 | 2017-12-12 22:56:15.213 | 33  | link   | ('issue', '476', 'messages')
>
>It looks like user 33 unlinked message 1514. It looks like all this
>did was to remove it from the issue_messages table. Should roundup
>have 'retired' message 1514 too?

No. There is no reason that a message can't be connected to multiple
issues. So unlinking it doesn't necessarily mean the message is
retired.

That being said, I don't think retiring it would do much. If a node is
retired it just doesn't show up in any method that lists the nodes
(think of a list of statuses). Generally you don't have a list of
messages in the UI. You can always access a retired node by requesting
it's designator (e.g msg12345, user33 etc.). I am not if retiring a
node that has full text search enabled will remove it from the text
search. If the msg (that is in FTS) is returned, does not have an
issue associated with it, it won't result in an issue being displayed.

Have a great rest of the week.
--
				-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.