Item10611: MongoDB sort order=createdate and order=modified weirdness

Compare the ordering of https://wiki.trin.org.au/Acacia/WebChanges with https://wiki.trin.org.au/Acacia/WebHome.

I'm still trying to untangle/isolate a nice simple test case, but maybe you can take a quick peek and see something obvious that I've missed (as to why WebChanges works and the WebHome search doesn't)

-- PaulHarvey - 08 Apr 2011

this may have been resolved by the m4 work - the 2 lists appear to be the same on my test today.

-- SvenDowideit - 19 Apr 2011

No The ordering is only correct as of whenever the webs were loaded into mongo.

-- PaulHarvey - 20 Apr 2011

The two topics linked in the first comment are now exposing another bug: deleting the TestTopic I had created to test the WebChanges vs WebHome date-modified bug, shows the deleted TestTopic in the WebHome SEARCH.

-- PaulHarvey - 20 Apr 2011

no, I'm sorry, you're going to have to re-test - this sounds way too much like the Listener wasn't enabled. I've just commited a change so that the Listener is always enabled - as the code is essentially useless without.

-- SvenDowideit - 22 Apr 2011

Cool, all seems good now - on both issues I noted.

-- PaulHarvey - 22 Apr 2011

is this a listener cfg issue?

-- SvenDowideit - 23 Apr 2011

or is this.... um... fastcgi, and the metacache we're using for our blinding speed.

-- SvenDowideit - 23 Apr 2011

nope, even more joyous:

inneresting there seems to be a difference in datatype in mongo the topic i edited has date:NumberLong(12341243123), whereas the loaded ones have... date:'1234214321'

-- SvenDowideit - 23 Apr 2011

yay - fixed something today.

-- SvenDowideit - 23 Apr 2011

Commenting is disabled while not logged in