Skip to content

Ambiguous message when executing sql: not an error:  #478

Closed

Description

@markawilliamson

So, here I am again :)

Previous version of the program issued standard confirmation message, query executed successfully..

now i get "not an error: "

guess that means a-ok?

basically the query was:
drop view blahblah;
create view blahblah as ....

Activity

  1. justinclift commented on Jan 6, 2016

    @justinclift
    Member

    Interesting. It sounds like things are ok, but lets ask @MKleusberg, as he made some changes with that code a while back (likely the change in question). 😄

  2. MKleusberg commented on Jan 27, 2016

    @MKleusberg
    Member

    Hmm, there's no 'not an error' string in our code and I can't seem to reproduce this 😕 Can you give us a more detailed description on how to reproduce this issue?

  3. justinclift commented on Jan 28, 2016

    @justinclift
    Member

    To me, it sounds like an output string from (say) SQLite after a successful statement execution.

  4. MKleusberg commented on Jan 6, 2017

    @MKleusberg
    Member

    Any updates on this? The "not an error" string is from SQLite but I don't see how it will be shown in the latest version of DB4S anymore.

  5. MKleusberg commented on Jan 27, 2017

    @MKleusberg
    Member

    Closing this because it's a really old issue and I believe it is fixed. If you can still reproduce this in the latest version, please re-open this issue, @thetazzbot 😃

  6. MKleusberg commented on Feb 1, 2017

    @MKleusberg
    Member

    Good news. Thanks to the same error message appearing in #957 and the comment by @chrisjlocke (which now seems to be deleted) I have managed to get a 'not an error' error message in the Execute SQL tab 😃 I have fixed this particular case now, so I'm more or less confident that this is finally fixed entirely now.

  7. chrisjlocke commented on Feb 2, 2017

    @chrisjlocke
    Member

    and the comment by @chrisjlocke (which now seems to be deleted)

    You stated you couldn't reproduce it, but I 'found a way' (nature always finds a way...) but I realised I was using v3.9.1. As soon as I tested the latest nightly, I couldn't reproduce it, so deleted the comment..... :) ... as I was talking gibberish!

  8. MKleusberg commented on Feb 2, 2017

    @MKleusberg
    Member

    @chrisjlocke No worries :D It helped me somehow provoking a 'not an error' error, so it definitely helped me ;)

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

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions