Re: How CLSQL finds and loads foreign libraries

On Thu, 21 Apr 2005 19:25:06 +0200, Edi Weitz wrote:

> On Thu, 21 Apr 2005 11:03:46 -0600, Kevin Rosenberg <kevin-HJRc7zDS/[email protected]> wrote:
> 
>> 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.
> 
> Yep.
> 
>> 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.

Could we make this customizable per backend? I'd suggest taking
ASDF:*central-registry* as a model - i.e. one list per backend. 
So a user can do:

  (pushnew "/opt/postgresql/lib/" clsql-postgresql:*libary-path* 
     :test #'equal)

This list should probably as a default contain the empty string (wich
signals to most dynamic loaders i know a "default" load path).

 Cheers Ralf Mattes