Re: lisp mail archive software

On Sun, Jul 06, 2003 at 08:11:52AM -0700, Miles Egan wrote:
> I'm leaning towards using
> postgresql as a back end, but that's going to make setup and
> installation a bit of a hassle.  Any opinions?

How are you accessing PostgreSQL? Which CL implementations are you using?

One alternative is SQLite, www.sqlite.org: 

- There is an open source LW interface to SQLite at the SQL level. 

- I have an UncommonSQL interface to same running on CMUCL. I think I
  also tested it a bit on LWW.

Personally, I find SQLite very useful: When performing risky code
refactoring, say, I simply make a copy of the database file and work on
that. If the outcome is bad, just chuck both code and data away. Makes it
easy to be courageous. ;-)

I'd originally envisaged to develop on SQLite and deploy on PostgreSQL
- both via UncommonSQL - but I ended up deploying on SQLite anyway.

Another alternative is SQL Relay, sqlrelay.sourceforge.net:

  SQL Relay is a persistent database connection pooling, proxying and load
  balancing system for Unix and Linux supporting ODBC, Oracle, MySQL, mSQL,
  PostgreSQL, Sybase, MS SQL Server, IBM DB2, Interbase, Lago and SQLite
  with APIs for C, C++, Perl, Perl-DBD, Python, Python-DB, Zope, PHP, Ruby,
  Ruby-DBD, TCL and Java, command line clients, a GUI configuration tool
  and extensive documentation.

Needs a CL FFI in this case. Of course, if the backend is still PostgreSQL,
setup and admin hassle remains, but perhaps SQL Relay is able to provide
some kind of backend independence for your code, if you aren't into
[Un]CommonSQL.


-- 
Ng Pheng Siong <[email protected]>