Table sort behaviour

[Matt Mower]

Hi David,

David A. Bayly wrote:

> My experience.  You must never open the table manually. If you set 
> target and then table.sortBy("value") it will preserve order 
> indefinitely. And, if you add an entry it will maintain order by value. 
> But if you modify an existing entry it will not resort. as it arguably 
> should. You can overcome this by deleting the entry and inserting again 
> instead..
> 

Thanks for the info.

To clarify these tables are being maintained on a server using code and 
would only be opened manually for diagnostic purposes.  The sort order 
is being set using the target.set/table.sortby combo.

What actually happened is that I was browsing our public W4 demo site 
and noticed on some topic pages that the posts were not appearing in the 
correct date order.

When I inspected some of the topic nodes in Frontier I noticed that the 
sort orders were not set as I would expect.  I wrote a quick script to 
iterate each topic node setting the correct sort order on it's posts table.

The next day browsing the site again I observed once more that some 
topic pages had the posts out of order and, when I checked, sure enough 
the tables were not date sorted.

I was in a hurry when I did the fix so I may have made a mistake or 
overlooked something, or possibly something else is at play here. But if 
seemed like Frontier had 'forgotten' the order being set.

I'll keep an eye out for it happening again and, if so, whether I can 
spot a pattern.

Thanks again for your experience.

Regards,

Matt