QSortFilterProxyModel trouble when inserting row

[saknopper]

Yes, it works perfectly.

I'm using Qt 4.2.2

[saknopper]

It's weird that when I calculate the position of the to be inserted row with model->rowCount() and then call insertRow() at that position. It still adds the row at the top of the table. While in your example in inserts the row at the bottom.

[jpn]

Hmm, so maybe it happens only when using QSortFilterProxyModel + QSqlTableModel?

[saknopper]

Perhaps... If that would be true, is there a way I can work around this problem that you know of?

[jpn]

Could you, by any chance, prepare a minimal example reproducing the problem we could play with? You could for example modify the earlier example of mine to use an SQLite db or so..

[saknopper]

Sure, I'll do that.

[saknopper]

I made an example with an in memory sqlite database for you, it illustrates the problem very clearly (in my opinion).

Some steps to reproduce the problem:

1) Sort on country (instead of id)
2) Add a new row
3) Enter for example "Italy" in the textbox
4) Press enter

The view resorts itself, but there's an empty row at the top.

Let me know if I can help you any further.

Thanks for looking into it.

[wysota]

Looks like the edit call causes the malfunction, probably because the "id" field is set to "0" instead of the proper index.

I changed the addRow() method and it works fine now:

void Table::addRow()
{
        int row = proxyModel->sourceModel()->rowCount();
        proxyModel->sourceModel()->insertRow(row);
        QModelIndex idx = proxyModel->sourceModel()->index(row, 1);
        if (idx.isValid())
        {
                proxyModel->sourceModel()->setData(idx.sibling(idx.row(), 0), row); // added here
                idx = proxyModel->mapFromSource(idx);
                setCurrentIndex(idx);
                edit(idx);
        }
}

void Table::addRow()
{
        int row = proxyModel->sourceModel()->rowCount();
        proxyModel->sourceModel()->insertRow(row);
        QModelIndex idx = proxyModel->sourceModel()->index(row, 1);
        if (idx.isValid())
        {
                proxyModel->sourceModel()->setData(idx.sibling(idx.row(), 0), row); // added here
                idx = proxyModel->mapFromSource(idx);
                setCurrentIndex(idx);
                edit(idx);
        }
}

To copy to clipboard, switch view to plain text mode 

[saknopper]

I'll check it out when I get home, thanks for helping!

[saknopper]

It's weird, but your solution which worked for you doesn't work for me.

When I add your line of code to the example program and add a new country the id gets set immediately with a value that's already present in de database. After editing the table doesn't get sorted either.

Are you also using Qt 4.2.2 with sqlite3?

[wysota]

When I add your line of code to the example program and add a new country the id gets set immediately with a value that's already present in de database. After editing the table doesn't get sorted either.

Try replacing the whole slot as I also changed the model calls to reference the source model everywhere. Also try moving the setData call out of the if statement - that was where I placed it at first. There shouldn't be any difference but who knows...

Are you also using Qt 4.2.2 with sqlite3?

I'm using 4.2.0 here, but that shouldn't matter.

[saknopper]

Try replacing the whole slot as I also changed the model calls to reference the source model everywhere. Also try moving the setData call out of the if statement - that was where I placed it at first. There shouldn't be any difference but who knows...

Waarrghhh, I'm going crazy. Still the same. I copy -> pasted the whole function and also placed the setData call out of the if statement. No changes though.

And indeed, adding AUTOINCREMENT doesn't solve it either.

[wysota]

I tested against Qt4.2.2. Looks like it works if you set an id which is already there (row), but doesn't if you pass a correct one (row+1). Anyway this is just cased by the way the sqltablemodel works. The proxy is just confused because the index changes. Reseting the model should help, but you'll lose selection and position of the view as it will also be reset.

[jpn]

I would have though that setting the column as "auto increment" could have solved the problem but seems not..

[wysota]

Can you provide a minimal compilable example reproducing the problem? I'd like to take a look...