[Bug Fix & Enhancement] Fixed sqlite3.OperationalError: no such table: timetable + update/delete timetable #32
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
tags: resolves #16 Added functions to update and delete timetable |
shravanasati
changed the title
shravanasati
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
tags: resolves #5 , resolves #6 , resolves #28
Fixed sqlite3.OperationalError: no such table: timetable
I've fixed the
sqlite3.OperationalError: no such table: timetableerror. The problem was that thecreateDBfunction was called only when there was notimetable.dbin the working directory, and not if the table was created in thetimetable.dbfile. So now thecreateDBis called everytime when the program starts, and it creates a tabletimetablein the filetimetable.dbonly when there is no such timetable.