Re: PR 1.2 update and messaging

"Vollmer Marius (Nokia-D/Helsinki)" <marius.vollmer@nokia.com> writes:

>> Checking the database
>> /home/user/.rtcom-eventlogger/el-v1.db or el.db with sqlite3 shows the old
>> messages in the database.
>
> Yes, and el-v1.db and el.db are _exactly_ the same size for me, so maybe
> some schema conversion failed and el.db is now in the wrong format or
> something and rtcom refuses to both read and write it. That's a very
> very uneducated guess of course.

Ok, turns out I was right again. :-(

el-v1.db is created by making a copy of el.db and then modifying its
schema in place. If that fails for any reason, el-v1.db is left in
place in the old format but assumed to have been converted and
apparently is then considered broken and rtcom refuses to use it.

All future call events and incoming text messages are lost.

<rant>
That's very very very bad, of course. At the least, rtcom should move
the 'corrupted' database to the side and create a new one so that new
events aren't lost. Plus a little dialog telling the user that the
impossible has happened.

(There is a ton of code in rtcom-messsagin-ui to deal with messages that
couldn't be saved, such as retrying to save them later, but that is all
in vain if the reason for failure doesn't go away. There is also code
to show an error dialog, but I haven't seen it.)
</rant>

Anyway, removing el-v1.db and el-v1.db-journal and then rebooting fixed
this for me. The database got correctly converted during boot and I
have all my conversations back (minus the one that got lost while the
database was in the wrong format).

Be sure to make a backup before removing el-v1.db, of course.

You can check whether el-v1.db is in the right format like this:

$ sqlite3 ~/.rtcom-eventlogger/el-v1.db
sqlite> .schema Events

If the Events table contains the "outgoing" column like this

CREATE TABLE Events (..., outgoing BOOL DEFAULT 0, ... );

then you have the right format.

> -----Original Message-----
> Anyway, removing el-v1.db and el-v1.db-journal and then rebooting fixed
> this for me. The database got correctly converted during boot and I
> have all my conversations back (minus the one that got lost while the
> database was in the wrong format).
>
> Be sure to make a backup before removing el-v1.db, of course.
>
> You can check whether el-v1.db is in the right format like this:
>
> $ sqlite3 ~/.rtcom-eventlogger/el-v1.db
> sqlite> .schema Events
>
> If the Events table contains the "outgoing" column like this
>
> CREATE TABLE Events (..., outgoing BOOL DEFAULT 0, ... );
>
> then you have the right format.

I moved el-v1.db and el-v1.db-journal to a different directory, rebooted,
and everything is working. Thanks for helping with this.

Aldon