ASQL compatibility update: Due to updates in the underlying components the two ASQL connectors have been updated to version 1.5 :
LIBASHMYSQL 1.5.145
LIBASHODBC 1.5.115
To allow for the latest A-Shell version to coexist with an earlier version, which is sometimes useful when testing updates, the search path for the libraries has been enhanced to first look for version 1.5 and then to fall back to the earlier/standard library version/name. Specifically:
Linux: Here the standard is to create a symbolic link from /usr/lib to the actual library module. For example:
/usr/lib/libashmysql.so.1 -> /vm/miame/bin/libashmysql.so.1.5.145.el7
/usr/lib/libashodbc.so.1 -> /vm/miame/bin/libashodbc.so.1.5.115.el7
Starting with this release, A-Shell will first try to link to the module with the .so.1.5 extension, and if not found, then fall back to the so.1.
For example, if you are running the latest A-Shell alongside an earlier version, you can set up your links as follows:
/usr/lib/libashmysql.so.1.5 -> /vm/miame/bin/libashmysql.so.1.5.145.el7
/usr/lib/libashmysql.so.1 -> /vm/miame/bin/libashmysql.so.1.4.143.el7
/usr/lib/libashodbc.so.1.5 -> /vm/miame/bin/libashodbc.so.1.5.115.el7
/usr/lib/libashodbc.so.1 -> /vm/miame/bin/libashodbc.so.1.4.113.el7
The newer A-Shell would use the .so.1.5 links while the older one would use the so.1 links. If you have only one version, then you can stick with the .so.1 extension.
Windows: Here the standard is to load the dll directly from the directory where the ashw32.exe executable was loaded from. The new version will look for a dll with -15.dll suffix first, and if not found, fall back to the standard name, e.g.:
c:\vm\miame\bin\libashmysql-15.dll ! version for 6.5.1715.13+
c:\vm\miame\bin\libashmysql.dll ! fallback / earlier versions
c:\vm\miame\bin\libashodbc-15.dll ! version for 6.5.1715.13+
c:\vm\miame\bin\libashodbc.dll ! fallback / earlier versionsEnter topic text here.
