You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
"select" request, the returned values are not displayed #1384
Sorry if I do not fully understand the problem. Are you saying that SELECT query in testSelectRequest.txt file returns nothing if the database is not saved?
I just tested it now using the same version (3.10.1) but on Win 7 and it seems to be working.
Can you show us a screenshot to help us understand the problem?
Yes, I got the same result as you posted in your screenshot. It happens when you reuse the same SQL tab. If you paste the query from testSqlScript.txt in the first tab (SQL 1) then reused the same tab to run the SELECT query in testSelectRequest.txt then you get the same result.
I don't know how this happened. I'm going to label this as a bug and hopefully someone can provide an answer.
That is odd - even if you use 'old' tabs, it works fine - but reuse that one tab, and yes, no results, even though it says it found 5 records. Even if you change the SQL, it still doesn't create the rows....
This is what I have discovered so far. The problem is exclusively on this pragma:
pragma foreign_keys =on;
Execute it on any tab to break it.
This is the responsible code. Removing it eliminates this problem:
// SQLite returns SQLITE_DONE when a valid SELECT statement was executed but returned no results. To run into the branch that updates// the status message and the table view anyway manipulate the status value here. This is also done for PRAGMA statements as they (sometimes)// return rows just like SELECT statements, too.if((query_part_type == SelectStatement || query_part_type == PragmaStatement) && sql3status == SQLITE_DONE)
sql3status = SQLITE_ROW;
I' ll try to follow, unless someone has it already clear.
@valbv I'm no longer able to reproduce this problem using the current code. This might have been a concurrency problem that it is now fixed by the changes done for PR #1394.
Activity
karim commentedon May 10, 2018
Sorry if I do not fully understand the problem. Are you saying that SELECT query in
testSelectRequest.txtfile returns nothing if the database is not saved?I just tested it now using the same version (3.10.1) but on Win 7 and it seems to be working.
Can you show us a screenshot to help us understand the problem?
valbv commentedon May 10, 2018
Sorry if i wrote my thoughts incorrect
Steps:
Result:

karim commentedon May 10, 2018
I see now the problem, thank you. 😃
Yes, I got the same result as you posted in your screenshot. It happens when you reuse the same SQL tab. If you paste the query from
testSqlScript.txtin the first tab (SQL 1) then reused the same tab to run the SELECT query intestSelectRequest.txtthen you get the same result.I don't know how this happened. I'm going to label this as a bug and hopefully someone can provide an answer.
chrisjlocke commentedon May 10, 2018
That is odd - even if you use 'old' tabs, it works fine - but reuse that one tab, and yes, no results, even though it says it found 5 records. Even if you change the SQL, it still doesn't create the rows....
mgrojo commentedon May 10, 2018
This is what I have discovered so far. The problem is exclusively on this pragma:
Execute it on any tab to break it.
This is the responsible code. Removing it eliminates this problem:
I' ll try to follow, unless someone has it already clear.
mgrojo commentedon Jun 10, 2018
@valbv I'm no longer able to reproduce this problem using the current code. This might have been a concurrency problem that it is now fixed by the changes done for PR #1394.
Please try with a nightly build and confirm that it is also solved for you, so we can close this issue.
https://nightlies.sqlitebrowser.org/latest/
justinclift commentedon Jun 11, 2018
Yeah, it's definitely possible. We've changed a lot of stuff, and done many bug fixes since the last major release.
valbv commentedon Jun 12, 2018
Yes, thanks!
justinclift commentedon Jun 12, 2018
@valbv That's a little bit unclear (to me). Are you meaning the problem is fixed in our nightly builds, so we should close this issue? 😄
valbv commentedon Jun 26, 2018
Problem fixed in nightly builds ;)
justinclift commentedon Jun 26, 2018
Awesome, thanks for confirming @valbv. 😄