ekeras12/22/2022, 12:34 PM
How would I solve it on my local machine? I'd configure /etc/odbcinst.ini in such a way:
[unixODBC][Driver Manager]Can't open lib 'FreeTDS' : file not found (0) (SQLDriverConnect)")
I tried the same on Orchest, but that doesn't fix the issue, because driver is not necessarily in the same location. In order to locate the needed location, I'd like to navigate through directories and see if it even exists. One way to do that on Orchest is to do
echo "[FreeTDS]\n\ Description = FreeTDS unixODBC Driver\n\ Driver = /usr/lib/x86_64-linux-gnu/odbc/libtdsodbc.so\n\ Setup = /usr/lib/x86_64-linux-gnu/odbc/libtdsS.so" | sudo tee -a /etc/odbcinst.ini
commands to find if file is existent while Setting up and environment. But as you can understand that's very inconvenient. My question: is there any other way how I could get to look into files? Or even better maybe you know a solution to FreeTDS issue?
is there any other way how I could get to look into files?There is! If you open a terminal in JupyterLab, then it will actually run inside one of your environments. Thus allowing you to interactively interact with your files (do note that changes are not persisted and the actual set-up needs to be in the Environment's setup script).
Or even better maybe you know a solution to FreeTDS issue?That would indeed be even better, but sadly I do not. Would have to look deeper into it.
ekeras12/22/2022, 1:13 PM