<para>Optimized loading of integer and floating-point fields.</para>
</listitem>
<listitem>
- <para>Additional database backends: &acl; ODBC and &sqlite;.</para>
+ <para>Additional database backends: &odbc;, &aodbc;, and &sqlite;.</para>
</listitem>
<listitem>
<para>A compatibility layer for &cmucl; specific code.</para>
implementations of &uffi;. The following implementations are supported:
</para>
<itemizedlist mark="opencircle">
- <listitem><para>&acl; v6.2 on Debian Linux, FreeBSD 4.5, and Microsoft Windows XP.</para></listitem>
- <listitem><para>&lw; v4.3 on Debian Linux and Microsoft Windows XP.</para></listitem>
- <listitem><para>&cmucl; 18e on Debian Linux, FreeBSD 4.5, and Solaris 2.8.</para></listitem>
- <listitem><para>&sbcl; 0.8.5 on Debian Linux.</para></listitem>
+ <listitem><para>&acl; v6.2 and 7.0b on Debian Linux x86 &
+ x86_64 & PowerPC, FreeBSD 4.5, and Microsoft Windows
+ XP.</para></listitem>
+ <listitem><para>&lw; v4.3 on Debian Linux and Microsoft
+ Windows XP.</para></listitem>
+ <listitem><para>&cmucl; 18e on Debian Linux, FreeBSD 4.5, and
+ Solaris 2.8.</para></listitem>
+ <listitem><para>&sbcl; 0.8.5 on Debian
+ Linux.</para></listitem>
<listitem><para>&scl; 1.1.1 on Debian Linux.</para></listitem>
- <listitem><para>&openmcl; 0.14 on Debian Linux PowerPC.</para></listitem>
+ <listitem><para>&openmcl; 0.14 on Debian Linux
+ PowerPC.</para></listitem>
</itemizedlist>
</sect2>
Currently, &clsql; supports the following databases:
</para>
<itemizedlist mark="opencircle">
- <listitem><para>&mysql; v3.23.51 and v4.0.15.</para></listitem>
- <listitem><para>&postgresql; v7.2 with both direct API and TCP
+ <listitem><para>&mysql; v3.23.51 and v4.0.18.</para></listitem>
+ <listitem><para>&postgresql; v7.4 with both direct API and TCP
socket connections.</para></listitem>
<listitem><para>&sqlite;.</para></listitem>
- <listitem><para>Allegro's ODBC interface (&aodbc;) using iODBC
- ODBC manager.</para></listitem>
+ <listitem><para>Direct &odbc; interface.</para></listitem>
+ <listitem><para>Allegro's DB interface (&aodbc;).</para></listitem>
</itemizedlist>
</sect2>
<screen>
(push #P"/usr/share/lisp/clsql/" asdf:*central-registry*)
-(asdf:operate 'asdf:load-op 'clsql-base) ; base CLSQL package
+(asdf:operate 'asdf:load-op 'clsql) ; main CLSQL package
(asdf:operate 'asdf:load-op 'clsql-mysql) ; MySQL interface
(asdf:operate 'asdf:load-op 'clsql-postgresql) ; PostgreSQL interface
(asdf:operate 'asdf:load-op 'clsql-postgresql-socket) ; Socket PGSQL interface
+(asdf:operate 'asdf:load-op 'clsql-odbc) ; ODBC interface
+(asdf:operate 'asdf:load-op 'clsql-sqlite) ; SQLite interface
(asdf:operate 'asdf:load-op 'clsql-aodbc) ; Allegro ODBC interface
-(asdf:operate 'asdf:load-op 'clsql) ; main CLSQL package
</screen>
</para>
</sect2>
configuration file named
<filename>.clsql-test.config</filename> must be created in
your home directory. There are instructures on the format of
- that file in the <filename>tests/tests.lisp</filename> file in
- the &clsql; source directory. After creating that file, you
- can run the test suite with &asdf;:
+ that file in the <filename>tests/README</filename>. After
+ creating <filename>.clsql-test.config</filename>, you can run
+ the test suite with &asdf;:
<screen>
(asdf:operate 'asdf:test-op 'clsql)
</screen>