![]() |
2010-11-17
, 13:18
|
Posts: 63 |
Thanked: 37 times |
Joined on Jul 2010
|
#2
|
![]() |
2010-11-18
, 03:44
|
Posts: 48 |
Thanked: 9 times |
Joined on Jan 2010
|
#3
|
![]() |
2010-11-18
, 06:11
|
|
Posts: 2,427 |
Thanked: 2,986 times |
Joined on Dec 2007
|
#4
|
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
|
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.
![]() |
2010-11-18
, 06:58
|
|
Posts: 2,427 |
Thanked: 2,986 times |
Joined on Dec 2007
|
#6
|
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.
![]() |
2010-11-20
, 18:36
|
|
Posts: 2,427 |
Thanked: 2,986 times |
Joined on Dec 2007
|
#7
|
sqlite3 <db file name/path> 'select max(id) from Events'
![]() |
2011-01-30
, 21:41
|
Posts: 4 |
Thanked: 0 times |
Joined on Jan 2011
@ Brazil
|
#8
|
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