Closed gdzqzzx closed 3 years ago
The problem seems to be that since version 1.4 SQLAlchemy has changed the type name from Binary
to BINARY
. I've pushed a commit that should fix it.
By the way it was my mistake to say you should run DenormaliseNVP.py
- if you want to convert from NVivo to another format you should run NormaliseNVP.py
. NormaliseDB.py
should also work if you have already attached the database but it is simpler to use NormaliseNVP.py
which will do the whole procedure. Plus I would like to get to the bottom of the issue you have encountered where the mounting process didn't work.
Thank you so much for the quick response!
I will test it again after your new comitting. Since my team is not going to use NVivo on next stage, I have more time to play with NVivotools and help to improve it now.
I have reopened #10, please let me know if you have further information you want to know there.
The problem seems to be that since version 1.4 SQLAlchemy has changed the type name from
Binary
toBINARY
. I've pushed a commit that should fix it.By the way it was my mistake to say you should run
DenormaliseNVP.py
- if you want to convert from NVivo to another format you should runNormaliseNVP.py
.NormaliseDB.py
should also work if you have already attached the database but it is simpler to useNormaliseNVP.py
which will do the whole procedure. Plus I would like to get to the bottom of the issue you have encountered where the mounting process didn't work.
Import Error in 1.4 SQLAlchemy is fixed
I'm using sqlAlchemy 1.4.7 and got following import error when running
python DenormaliseDB.py
andpython NormaliseDB.py
(test only, no input parameters):It seems that somehow the query returned
bytes
as mentioned here.