Skip to content

Database Changed Heuristics - False Flag? #1297

Open

Description

@sky5walk

Details for the issue

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'm opening this issue because:

  • DB4S is crashing
  • DB4S has a bug
  • DB4S needs a feature
  • DB4S has another problem

I'm using DB4S on:

  • Windows: ( version:10 Pro_ )
  • Linux: ( distro: ___ )
  • Mac OS: ( version: ___ )
  • Other: ___

I'm using DB4S version:

  • 3.10.1
  • 3.10.0
  • 3.9.1
  • Other: ___

I have also:

Activity

  1. sky5walk commented on Sep 19, 2018

    @sky5walk
    Author

    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.
    
  2. added
    bugConfirmed bugs or reports that are very likely to be bugs.
    and removed on Sep 19, 2018
  3. mgrojo commented on Sep 19, 2018

    @mgrojo
    Member

    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

  4. justinclift commented on Sep 19, 2018

    @justinclift
    Member

    Good find @sky5walk. 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugConfirmed bugs or reports that are very likely to be bugs.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions