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
I would like DB4S to improve its "Database Changed" heuristics.
Maybe parse the SQL text for "CREATE, ALTER, UPDATE, etc."?
Useful extra information
Ex. SQL code triggering "Database Changed".
--< START DELAY
WITH RECURSIVE
cnt(x) AS (VALUES(1) UNION ALL SELECT x+1 FROM cnt WHERE x<1e6)
SELECT x FROM cnt WHERE x=0;
--< END DELAY
I have found several queries that create a FALSE flag for Database changed.
Any chance to bump this topic to BUGS?
--Open a database
--Execute the following in a Execute SQL tab:
SELECT * FROM main.sqlite_master; --< This prompts the Write/Revert Changes gui prompt!
--ATTACH 'c:\mydatabase' AS db2; Also prompts Write/Revert Changes.
--Click 'Write Changes' and the Flag becomes grayed but the database file remains unchanged?
--This confirms the False Flag bug.
This can be considered a bug, both your first example and this later one. But the later is more severe: just a single select statement followed by a space is triggering it. I'll take a look when I have some time
Activity
sky5walk commentedon Sep 19, 2018
I have found several queries that create a FALSE flag for Database changed.
Any chance to bump this topic to BUGS?
mgrojo commentedon Sep 19, 2018
This can be considered a bug, both your first example and this later one. But the later is more severe: just a single select statement followed by a space is triggering it. I'll take a look when I have some time
justinclift commentedon Sep 19, 2018
Good find @sky5walk. 😄