commonsense team mailing list archive

[Ken Arnold <kenneth.arnold@xxxxxxxxx>]

Public bug reported:

sqlite3 has the behavior that opening a nonexistent database file
doesn't fail; it silently creates the db.

This means that people using the sqlite configuration don't find out
that something is misconfigured until something tries to access the
database and finds that the tables don't exist.

Instead, the sqlite config should check that the database file exists
and fail (with an exception that's not ImportError) to import `settings`
if it's missing.

** Affects: conceptnet
     Importance: Undecided
         Status: New

-- 
sqlite config should warn/fail early if the database does not exist.
https://bugs.launchpad.net/bugs/377460
You received this bug notification because you are a member of
Commonsense Computing, which is the registrant for ConceptNet.

Status in ConceptNet API: New

Bug description:
sqlite3 has the behavior that opening a nonexistent database file doesn't fail; it silently creates the db.

This means that people using the sqlite configuration don't find out that something is misconfigured until something tries to access the database and finds that the tables don't exist.

Instead, the sqlite config should check that the database file exists and fail (with an exception that's not ImportError) to import `settings` if it's missing.