Project

General

Profile

Bug #1036

Removing Network, "dangling" backlogs and buffers in db.

Added by JabLuszko about 14 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Quassel Core
Target version:
-
Start date:
11/08/2010
Due date:
% Done:

0%

Estimated time:
Version:
0.6.2
OS:
Any

Description

When you remove Network via Quassel Client there are still some backlogs/buffers left which prevent users migration from sqlite to postresql.

sqlite> select br.bufferid, br.networkid, br.buffername, br.buffertype from buffer br left join network nw using(networkid) where nw.networkid is null;
11|2||1
229|8|#rootnode|2
230|8|#offchat|2
231|0|#test|2
sqlite> select * from backlog where bufferid=11;
541|1272246369|11|1024|0|1|Disconnecting. (Quit.)
sqlite> select * from backlog where bufferid=229;
875826|1287598103|229|128|0|15642|Client Quit
sqlite> select * from backlog where bufferid=230;
875827|1287598104|230|128|0|15642|Client Quit
sqlite> select * from backlog where bufferid=231;
875828|1287598104|231|128|0|15642|Client Quit

Looks like the quassel is re-inserting my quits to database, even if the Network is being deleted. It is happening only for some buffers, not all.
I was running quasselcore for two users, it only happend for one of them when he was deleting all his networks at once.

Also available in: Atom PDF