Re: How CLSQL finds and loads foreign libraries

Edi Weitz wrote:
> So, in that case I fully agree with you - I think absolute paths
> should be removed from CLSQL or made optional.  I'd be willing to
> provide a patch if Kevin agrees.

Thanks for the thoughts, Edi and Michael.

I agree that abstracting the foreign library loader code is a good
idea. The abstracted code could go into a new file in the sql/
directory and the specific loading specializations could go into the
*-loader.lisp files in the db-mysql, db-postgresql, db-oracle,
db-odbc, db-sqlite, and db-sqlite3 (whew!) directories.

Edi, I think your idea to have a way for the end-user to set local
directories is a good idea so that the CLSQL source itself doesn't
need to be edited by the end-user. Michael, taking advantage of
Windows ability to find shared libraries is an advantage. Does this
only work if the directory with the shared library is the current PATH
environmental variable?

-- 
Kevin Rosenberg
kevin-HJRc7zDS/[email protected]