Harald Fernengel wrote:
> Hi,
>
> On Tuesday 11 September 2012 14:49:22 ext Mark Brand wrote:
>> We could consider removing the row from the model only after verifying
>> that the corresponding record no longer exists in the database table.
> One principle of the SQL module was not to try to outsma
Hi,
On Tuesday 11 September 2012 14:49:22 ext Mark Brand wrote:
> We could consider removing the row from the model only after verifying
> that the corresponding record no longer exists in the database table.
One principle of the SQL module was not to try to outsmart the database. We
use static
Maemi Carrer wrote:
>> ... each edit causes the table to be requeried and the model reset, which
>> breaks navigation in the view.
> Do you mind elaborating in which way this breaks navigation?
In Qt 4, QSqlTableModel calls select() immediately after submitting
changes to the database. This invo
Thank you for your response!
2012/8/14 Mark Brand :
> QSqlTableModel has had some major changes for Qt5. The changes file
> "dist/changes-5.0.0" lists them.
I totally missed that.
> ... each edit causes the table to be requeried and the model reset, which
> breaks navigation in the view.
Do you
Maemi Carrer wrote:
> Hello!
>
> When porting from Qt4 to Qt5 I've noticed a behavorial change in
> QSqlTableModel (I've attached a small example).
QSqlTableModel has had some major changes for Qt5. The changes file
"dist/changes-5.0.0" lists them. Many of the changes are related to
making the O
Hello!
When porting from Qt4 to Qt5 I've noticed a behavorial change in
QSqlTableModel (I've attached a small example).
Situation: QSqlTableModel set on a QSqlTableView
Action: Delete row using deleteRow()
Qt4 behavior: delete row from model and from table view
Qt5 behaviour: delete row from mod
