Parent Directory | Revision Log
|Links to HEAD:||(view) (annotate)|
|Links to HEAD:||(view) (annotate)|
Allow encoding used for socket communication with the backend to be specified as a keyword argument to PG-CONNECT, for cases where rebinding *PG-CLIENT-ENCODING* is inconvenient. Add a simple test for encoding support. (From Attila Lendvai <firstname.lastname@example.org>)
Add unix-domain socket support for Allegro CL (tested with Express edition for Linux/x86).
Disabling buffering of the socket stream on CLISP greatly improves performance.
- on CL implementations that support Unix sockets, the HOST argument to PG-CONNECT may designate the directory containing the local PostgreSQL unix socket (often "/var/run/postgresql/"). The HOST argument is assumed to designate a local directory rather than a hostname when its first character is #\/. You may need to modify authentication options in the PostgreSQL configuration file pg_hba.conf to allow connections over a unix-domain socket where the databse username is not equal to your ident tokens. This is an incompatible change to previous support for unix-domain sockets with CMUCL (previously a HOST of NIL told pg-dot-lisp to connect to a unix-domain socket whose name was hardwired into the library). This support currently exists for SBCL, CMUCL and OpenMCL.
Make comparison in IMPLEMENTATION-NAME-FOR-ENCODING case-insensitive (from email@example.com).
Fix for encoding support for CLISP and OpenMCL (encoding still not working correctly). OpenMCL fix from Risto Laakso.
Fix the SB-ROTATE-BYTE dependency for SBCL (was loaded twice, with unfortunate consequences). Add support for unix-socket connections to the backend for SBCL. (Thanks to Andreas Fuchs)
Fix sockets for recent ABCL versions. Modify the client-encoding code to work with multiple implementations (incomplete testing).
Modified sbcl unicode support, works for me. Moved requires into asdf package, otherwise we get asdf package problems, unknown if it works with other lisps
Use the updated MD5 code, that operates on octet arrays rather than strings.
Three fixes from Björn Lindberg <firstname.lastname@example.org>: - Two trivial bugs with regards to use with Allegro - Handling of the special timestamp values infinity and -infinity. They gave an error, but now returns the symbols :INFINITY and :-INFINITY respectively. - A bug in the version 3 of the protocol, where it would return NIL for fields in the database containing the empty string, rather than an empty string.
possible sbcl unicode fix
add a file that does a manual load of pg
- add md5 authentication (thanks to Brian Mastenbrook). Uses Pierre Mai's portable md5.lisp library, that has been added to the project (with extra EVAL-WHENness to please OpenMCL and ACL). Tested with CMUCL, SBCL, OpenMCL, CLISP, ACL 6.1. ABCL does not compile md5.lisp, probably for more EVAL-WHEN reasons. Only tested with PostgreSQL version 7.4.
- changes for Armed Bear Lisp: change to new API for binary socket streams; autoload a working FORMAT
- improvements to the system-dependent functionality: OpenMCL is able to use a local connection to the backend; most implementations resignal connection errors as a postgres-error. - fixes to the lowlevel code
Integrate Peter Van Eynde's v3 protocol support: - create PGCON-V2 and PGCON-V3 classes - PG-CONNECT attempts to connect using v3 protocol, and falls back to v2 protocol for older backends; return a PGCON-V2 or PGCON-V3 object - PG-EXEC and FN and PG-DISCONNECT are generic functions that dispatch on the connection type - protocol code split into v2-protocol.lisp and v3-protocol.lisp TBD: cleaning up the notification & error reporting support, and factorizing more code between the two protocol versions. Also split code out into multiple files: - large-object support - metainformation about databases - parsing and type coercion support - utility functions and macros
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, select a symbolic revision name using the selection box, or choose 'Use Text Field' and enter a numeric revision.
|Powered by ViewVC 1.1.5|