Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: address issues of sqlite backend #19

Closed
wants to merge 1 commit into from

Conversation

flavio
Copy link
Contributor

@flavio flavio commented Jun 28, 2024

Using sqlite to save checkpoints failed at runtime because:

  • Internal Mutex was a nil pointer
  • The help messages explaining how to create the sqlite3 database had the wrong CREATE statement
  • The implementation of the LockBackend interface had the Fetch function return a wrong object (a dynamoCheckpoint instead of a sqliteCheckpoint)

Using sqlite to save checkpoints failed at runtime because:

* Internal Mutex was a nil pointer
* The help messages explaining how to create the sqlite3 database had
  the wrong CREATE statement
* The implementation of the `LockBackend` interface had the `Fetch`
  function return a wrong object (a `dynamoCheckpoint` instead of a
  `sqliteCheckpoint`)

Signed-off-by: Flavio Castelli <fcastelli@suse.com>
@flavio flavio mentioned this pull request Jun 28, 2024
FiloSottile pushed a commit that referenced this pull request Aug 7, 2024
Using sqlite to save checkpoints failed at runtime because:

* Internal Mutex was a nil pointer
* The help messages explaining how to create the sqlite3 database had
  the wrong CREATE statement
* The implementation of the `LockBackend` interface had the `Fetch`
  function return a wrong object (a `dynamoCheckpoint` instead of a
  `sqliteCheckpoint`)

Closes #19

Signed-off-by: Flavio Castelli <fcastelli@suse.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant