Open balarsen opened 3 years ago
Ah, you're talking empty, not nonexistent (which was my first thought). I think this problem is consistent across database backends so doesn't have to wait for #14. It sort of relates to #7 where there should be some basic db structure checks when DButils
is instantiated.
Ah, you're talking empty, not nonexistent (which was my first thought). I think this problem is consistent across database backends so doesn't have to wait for #14. It sort of relates to #7 where there should be some basic db structure checks when
DButils
is instantiated.
Yeah the nonexistent seems good
$ ~/dbUtils/ProcessQueue.py -i -m asjkdhakhjds
Traceback (most recent call last):
File "/home/ectsoc/dbUtils/ProcessQueue.py", line 78, in <module>
pq = dbprocessing.ProcessQueue(options.mission, dryrun=options.dryrun, echo=options.echo)
File "/home/ectsoc/.local/lib/python2.7/site-packages/dbprocessing/dbprocessing.py", line 44, in __init__
dbu = DButils.DButils(self.mission, echo=echo)
File "/home/ectsoc/.local/lib/python2.7/site-packages/dbprocessing/DButils.py", line 89, in __init__
self.openDB(db_var=db_var, engine=engine, echo=echo)
File "/home/ectsoc/.local/lib/python2.7/site-packages/dbprocessing/DButils.py", line 150, in openDB
raise (ValueError("DB file specified doesn't exist"))
ValueError: DB file specified doesn't exist
I've been bitten before too many times by sqlite assuming if the file doesn't exist I just want to go ahead and start from scratch :)
(The Brian breaking stuff begins...)
When ProcessQueue.py is run on an empty database the message is really cryptic.
Minimal example to reproduce issue:
Error message/Traceback:
OS, Python version, and dependency version information:
Version of dbprocessing
36b441db80d2bf5f6bf1ea3d111304edea56571b
Closure condition
This issue should be closed when the error message says something closer to "empty database"