Okay, so it's not interesting to keep both DB schemes if it is is properly
converted on upgrades. Downgrading is not a supported operation AFAIK…
Looks sane to mark this report as invalid isn't it? Feel free to reopen that
bug if you think I'm wrong!
** Changed in: gajim (Ubuntu)
Status:
I tried gajim from upstream trunk some time ago. So it could be due to a
version downgrade.
--
table unread_messages has 3 columns but 2 values were supplied
https://bugs.launchpad.net/bugs/462043
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
I believe this happened for me as I upgraded gajim to 0.13.* by hands and then
downgraded back to stock 0.12.5…
Did you do something similar?
** Changed in: gajim (Ubuntu)
Status: New => Incomplete
--
table unread_messages has 3 columns but 2 values were supplied
https://bugs.launchpad.
Has the DB schema for unread_messages changed between Gajim versions?
If so, it would be good if both the old and the new schema were
supported. Something like
def insert_unread_events(self, message_id, jid_id):
''' add unread message with id: message_id'''
To get rid of this error, I removed "~/.gajim/logs.db".
--
table unread_messages has 3 columns but 2 values were supplied
https://bugs.launchpad.net/bugs/462043
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/34488605/Dependencies.txt
** Attachment added: "XsessionErrors.txt"
http://launchpadlibrarian.net/34488606/XsessionErrors.txt
--
table unread_messages has 3 columns but 2 values were supplied
https://bugs.launchpad.net/
