View Single Post
Posts: 20 | Thanked: 15 times | Joined on Dec 2009
#69
Originally Posted by flux View Post
After running smsimporter, I updated the el.db with sqlite3 with "update events set storage_time = start_time" and the order in the conversation view didn't change (even after a reboot). I'm thinking it uses the ID numbers for ordering, so I suppose I will try to renumber the messages at some point. (..I hope there are no references to the ID-number, it didn't look that way..) However, I will likely try it only once I get to import very many more messages from my old trusty 9300i - once I get its display fixed..
I had tried this a few days ago with the same result. Could it be perhaps that Conversations caches the order and there just hasn't been a trigger to refresh the records? When rtcom-eventlogger methods are used to insert records, for example, a D-Bus signal is sent to notify applications about the change. Since we modified the db directly, no such signal was sent. That said, I don't know if there is a signal for changes in storage_time. For more details, see http://maemo.gitorious.org/maemo-rtc...es/Eventlogger.

Is there a way to determine what field(s) the Conversations application is using to determine sort order?