Re: [Interest] QML readTransaction tx.executeSql SELECT is returning rowsAffected=1

P1: Critical https://bugreports.qt.io/browse/QTBUG-53412 ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Bug reproduction needed!

I forgot to mention, could you send your qt version? I am seeing this on qt 5.4.2 Thanks, Etienne ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QML readTransaction tx.executeSql SELECT is returning rowsAffected=1

I *think* I'm on to something. It looks like Qt re-uses the rs object and just updates the fields as needed. What is also happening is the insert statement is: inserting '' values (0-length strings) , which Qt is converting to nulls. sqlite> .nullvalue # sqlite> select rowid, * from responses;

[Interest] QML readTransaction tx.executeSql SELECT is returning rowsAffected=1

I've just started seeing a problem in my application that's been working fine for months. While the rowId corresponds to the last inserted row, I'm getting it in a subsequent SELECT transaction. db.transaction( function (tx) { var sql = "INSERT INTO responses (status, server) VALUES (

[Interest] QtQuick Window visible property

Hi, Lets consider the following example- ApplicationWindow { visible: true width: 640 height: 480 Button { id: button checkable: true text: "Hello" } Window { id: window2 visible: button.checked } } So essentially whenever

Re: [Interest] Raster Engine Issues

Also, -fsanitize=address ; -fsanitize=undefined. On Fri, Jun 10, 2016 at 9:27 AM, Harri Porten wrote: > On Thu, 9 Jun 2016, Alper Sağlam wrote: > > I am deailing with qt backtrace from a core file, it looks like it is not >> reproducible (sporadic) and happened three