-
Notifications
You must be signed in to change notification settings - Fork 635
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Handle CLI errors more gracefully #16
Labels
Milestone
Comments
I know this is an old issue but I am currently working on solving:
Should |
rluzuriaga
added a commit
to rluzuriaga/pokedex
that referenced
this issue
Apr 2, 2020
- Add exception handling for SQLite, PostgreSQL, and MySQL. Sqlalchemy gives different exceptions for each database engine so I have seperated each exception for each engine. The error message passed by each engine is also different so that is checked as well. - Once the function gets one of those exceptions the following message is outputed and the program ends: `ERROR: Table 'TABLENAME' already exists in the database. Did you mean to use 'pokedex load -D'` - If the error is not that a table already exists, then the output will just be the full error from sqlalchemy. That way if someone runs into that error it can be reported as an issue and whoever can help would see the full error. --- Resolves part of issue veekun#16
magical
pushed a commit
that referenced
this issue
Jun 17, 2020
- Add exception handling for SQLite, PostgreSQL, and MySQL. Sqlalchemy gives different exceptions for each database engine so I have seperated each exception for each engine. The error message passed by each engine is also different so that is checked as well. - Once the function gets one of those exceptions the following message is outputed and the program ends: `ERROR: Table 'TABLENAME' already exists in the database. Did you mean to use 'pokedex load -D'` - If the error is not that a table already exists, then the output will just be the full error from sqlalchemy. That way if someone runs into that error it can be reported as an issue and whoever can help would see the full error. --- Resolves part of issue #16
magical
pushed a commit
that referenced
this issue
Jun 17, 2020
- Add exception handling for SQLite, PostgreSQL, and MySQL. Sqlalchemy gives different exceptions for each database engine so I have seperated each exception for each engine. The error message passed by each engine is also different so that is checked as well. - Once the function gets one of those exceptions the following message is outputed and the program ends: `ERROR: Table 'TABLENAME' already exists in the database. Did you mean to use 'pokedex load -D'` - If the error is not that a table already exists, then the output will just be the full error from sqlalchemy. That way if someone runs into that error it can be reported as an issue and whoever can help would see the full error. --- Resolves part of issue #16
OpulentOwl
added a commit
to OpulentOwl/pokedex
that referenced
this issue
Apr 18, 2022
…tatus/whatever command.) Modified lookup so when index does not exist the full stacktrace is not printed.
OpulentOwl
added a commit
to OpulentOwl/pokedex
that referenced
this issue
Apr 22, 2022
…tatus/whatever command.) Modified lookup so when index does not exist the full stacktrace is not printed.
OpulentOwl
added a commit
to OpulentOwl/pokedex
that referenced
this issue
May 2, 2022
…lity is correct when index is not present
OpulentOwl
added a commit
to OpulentOwl/pokedex
that referenced
this issue
May 2, 2022
OpulentOwl
added a commit
to OpulentOwl/pokedex
that referenced
this issue
May 2, 2022
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Reported by Eevee on 2010/04/24 15:31:40 +0000 · Migrated from Redmine issue 217
Off the top of my head, the following can happen:
dump
tries to dump from an obsolete schema.load
is given an incomplete subtree of dependent tables.load
tries to load into existing tables without-D
passed.Showing a backtrace is ugly and, for many of these, not very helpful.
Comment by Eevee from 2010/10/08 08:00:28 +0000
The text was updated successfully, but these errors were encountered: