Active Topics
-
Porting apps to Leste (29)
to Maemo 7 / Leste by Arno_11 - 2 days, 18 hrs ago -
Install Fonts in N900 (68)
to Maemo 5 / Fremantle by teroyk - 3 days, 21 hrs ago - more...
|
2010-11-17
, 13:18
|
|
Posts: 63 |
Thanked: 37 times |
Joined on Jul 2010
|
#2
|
I have the same problem.
The el-v1.db does not get updated when new messages arrive.
When I move it, a new one will be created that works.
However I want to merge it with the old one or fix the old one so it gets updated again
Anyone?
The el-v1.db does not get updated when new messages arrive.
When I move it, a new one will be created that works.
However I want to merge it with the old one or fix the old one so it gets updated again
Anyone?
|
|
2010-11-18
, 03:44
|
|
Posts: 48 |
Thanked: 9 times |
Joined on Jan 2010
|
#3
|
Someone really needs to fix this.
 |
|
2010-11-18
, 06:11
|
|
Posts: 2,427 |
Thanked: 2,986 times |
Joined on Dec 2007
|
#4
|
I think I can help, but I won't be able to look at this for a few days. In the meantime, make good, safe copies of everything to a backup folder. Maybe even to another computer.
All should be well. I have dumped, deleted and restored specific conversations from this database before, and I am familiar with its tables and their schemas. If you're tech savvy and ambitious, I encourage you to familiarize yourself with the sqlite3 command line tool. It will play a big role in the restoration.
Last edited by daperl; 2010-11-18 at 06:16.
All should be well. I have dumped, deleted and restored specific conversations from this database before, and I am familiar with its tables and their schemas. If you're tech savvy and ambitious, I encourage you to familiarize yourself with the sqlite3 command line tool. It will play a big role in the restoration.
__________________
N9: Go white or go home
N9: Go white or go home
Last edited by daperl; 2010-11-18 at 06:16.
| The Following User Says Thank You to daperl For This Useful Post: | ||
|
|
2010-11-18
, 06:19
|
|
Posts: 48 |
Thanked: 9 times |
Joined on Jan 2010
|
#5
|
Originally Posted by daperl
I'm familiar with the use of SQLite. Are these files standard SQLite databases, i.e., there's nothing non-standard? If yes, then instruction applicable to SQLite, will directly apply to our concerns.
I think I can help, but I won't be able to look at this for a few days. In the meantime, make good, safe copies of everything to a backup folder. Maybe even to another computer.
All should be well. I have dumped, deleted and restored specific conversations from this database before, and I am familiar with its tables and their schemas. If you're tech savvy and ambitious, I encourage you to familiarize yourself with the sqlite3 command line tool. It will play a big role in the restoration.
I'm curious to know, what specifically, causes the behavior in the bugs that our concerns point to.
|
|
2010-11-18
, 06:58
|
|
Posts: 2,427 |
Thanked: 2,986 times |
Joined on Dec 2007
|
#6
|
Originally Posted by ebzzry
Yes, this is just a standard sqlite database. I'm not familiar with the SMS problems. Since PR 1.3, I've only been using Conversations for IM, and I haven't had any issues. Sorry.
I'm familiar with the use of SQLite. Are these files standard SQLite databases, i.e., there's nothing non-standard? If yes, then instruction applicable to SQLite, will directly apply to our concerns.
I'm curious to know, what specifically, causes the behavior in the bugs that our concerns point to.
Anyway, the most important piece to the merge puzzle is making sure the 'Events' table primary key ('id') is unique across both databases. And there's more than one way to make that happen.
__________________
N9: Go white or go home
N9: Go white or go home
|
|
2010-11-20
, 18:36
|
|
Posts: 2,427 |
Thanked: 2,986 times |
Joined on Dec 2007
|
#7
|
Okay guys, give me a chronology of the problem with as much detail as you feel is necessary. Also, run this command for all databases of interest and post the output with good labeling:
Code:
sqlite3 <db file name/path> 'select max(id) from Events'
__________________
N9: Go white or go home
N9: Go white or go home
|
|
2011-01-30
, 21:41
|
|
Posts: 4 |
Thanked: 0 times |
Joined on Jan 2011
@ Brazil
|
#8
|
Hello guys, for anyone that interests, I made a small PHP script that do some kind of early merging of multiple el-v1.db. But the N900 gets unable to manipulate the resulting DB, since it isn't according to the DB itself way of use. It needs some caching (on the GroupCache for example) that I haven't done yet. Some research is needed before, including direct intervention on the DB. Have fun.
http://pastebin.com/R1eBqVNT
http://pastebin.com/R1eBqVNT
I have previously backed up an older version of this file, about two weeks ago, and I deleted that file (so the system can create a new one) just to have a working logging facility. It was due to the conversations bugs (I'm sorry, I forgot the bug IDs) related with PR 1.3, wherein:
1- New messages, be it SMS or IM, are not logged, i.e., the file /home/user/.rtcom-eventlogger/el-v1.db is not updated
2- The Conversations app does not display updates when receiving or sending messages