Skip to content

How to avoid errors in the debugger? #14

Description

@hyotang666

sqlite-constraint-error is signaled in the debugger REPL when the debugger is invoked with sqlite-constraint-error then the restart abort is selected.

The minimum example is below.

* (sqlite:with-open-database (db ":memory:")
  (sqlite:execute-non-query db "create table demo (name tinytext unique,id integer)")
  (sqlite:execute-non-query db "insert into demo (name, id) values (\"foo\", 1)")
  (sqlite:execute-non-query db "insert into demo (name, id) values (\"foo\", 2)"))

debugger invoked on a SQLITE:SQLITE-CONSTRAINT-ERROR in thread
#<THREAD "main thread" RUNNING {10014E4073}>:
  Error while stepping an sqlite statement.
Code CONSTRAINT: UNIQUE constraint failed: demo.name.
Database: :memory:
SQL: insert into demo (name, id) values ("foo", 2)

 0: [ABORT] Exit debugger, returning to top level.

0] 0

debugger invoked on a SQLITE:SQLITE-CONSTRAINT-ERROR in thread
#<THREAD "main thread" RUNNING {10014E4073}>:
  Error while resetting an sqlite statement.
Code CONSTRAINT: UNIQUE constraint failed: demo.name.
Database: :memory:
SQL: insert into demo (name, id) values ("foo", 2)

 0: [ABORT] Exit debugger, returning to top level.

0] 0

Activity

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

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions