quarkslab/irma-common

IRMA common

irma-common's Issues

Incompatible database options

@guillaumededrie, @ch0k0bn, I have a problem with this commit with an already provisioned frontend. If the database does not use UTF-8 from the beginning, the frontend_app cannot start and fails with a database connection error.

What do you suggest ? We should planify to add a migration script ? FYI, at the moment, this code is not used in any repository (version is forced by submodules). Thus, this is not at all a P1 issue, as far as no body need to display and store files with utf8 special characters in their database.

fix disconnect() in nosqlhandler

We need to:

1. create a handle in the constructor
2. in each function, check if connected or not, and reconnect if needed

IRMA python modules name confusion

As the irma-cli Python module is installed under the name irma, and some parts of irma-common are importing irma.XXX, if both are installed in the same namespace, conflicts occur.
(Additionally, the PEP8 highly discouraged relative import to avoid this kind of bugs and confusion in code reading)