Ignore-this: 2b99de6a8b7a2e9ef38f262940e79eaa

darcs-hash:7fc547734964e8448f3d62016719c96ed886db94

Ignore-this: 88bc886ac661866cb5ac5c6ac776753

darcs-hash:d2ffa2e31ceb747a0bc5341baa849d6e5b25f5fb

use built-in socket library on SBCL, drop usocket dependency on that platform. also allow a host of :unix to be passed in to try and use local unix socket to connect to the server (only on SBCL)

Ignore-this: ebc68551b84a78a4435e9b741cf3581a

darcs-hash:04aec715306b35905ca1e78f1f54740794ed853c

Ignore-this: fec903b2178c1d096e5e31ce4b034565

darcs-hash:dd6bed1b06d59a78e3b4692a2612f2fdf5bcf35f

Ignore-this: 3bf1a6d7c66bb53424605af630dae59f

darcs-hash:2138542209981a9ae312ed438eafdd77f6e407bf

Ignore-this: 1e00e7831455c35325af44d457aefc4f

darcs-hash:8449c6d1cb1c50017c40e6745160fea9b23b25b2

added a write-rational-as-foating-point function and use it to serialize rationals when sending them to Postgres.

Ignore-this: 45c9cc579792d173983382218dbfbac1

it limits their length at 38 digits and throws an error if they don't fit (instead of silently losing precision as it did before).

with this change storing 0.7 into a NUMERIC column will properly read back as 0.7.

darcs-hash:8e583359be6893f86e1458d7085db2852d4e354c

darcs-hash:931359f2ed43016dd9781c011544dac6d7c4a8e6

darcs-hash:9b5c91cb807c252a8374956147a787f5a79daf2b

darcs-hash:7eada497b6e12d128b689551f77b3603e7e31e44

darcs-hash:4014996db54e1dd0f9db3e41d1c4f2de0639e1a1

Ignore-this: af1d8d6f9b64498aeeb0e1f0fe7c054c

darcs-hash:ec8298c2e077073f9be6f37af634f07423c9e822

On Clozure CL (PPC32), (format "~f" (coerce 1/123 'double-float))
returns "0.008130081300813009D0" which is not a number syntax
PostgreSQL understands.

In order to be sure that a format is used that is always supported,
the formatting string was changed to generate the number in
exponential notation which is accepted by PostgreSQL and which can be
reliably generated by at least SBCL and Clozure CL (only CLs I've
tested).

The modified control string in this patch ("~,,,,,,'EE") will generate
for the rational 1/123 "8.130081300813009E-3" which is accepted and
interpreted properly by PostgreSQL.

darcs-hash:fe44e973cb94cbb6796a4b04c7d13ce56a9c8b85

darcs-hash:470a0007019c35a184d20dc11e5af201b38cf0cd

darcs-hash:8fb06e3055ac06a794941a3a26faf4425d00b06d

darcs-hash:efdfc7e1599bc11ac9b342f92b4b867a0024e759

darcs-hash:99658d8e160bfab755ecba06b789765f07245afb

darcs-hash:bc6d70930c57a3d980b6c2e6785233f2445fcf3f

darcs-hash:0b9f8172f840a7f32e7592fd101acfbf0951717c

darcs-hash:b1b101690497fc0820ee04e4d97d99ec720b2ed1

darcs-hash:8b1c17af86687786759d2f03f9b12d75a14182b2

fix syncing, which was causing the library to hang on a socket read when an error happened at the wrong moment

darcs-hash:97d9834f9d410ee2c36cb8b6f1e04c22f468e5dc

darcs-hash:21e78403ddbd4318aaa1063e204b4c31e9dc08e8

darcs-hash:801f80315f05c5db6d6ce114d3e5162faa05591c

darcs-hash:0c3d98d1522eaa566ce0b6e3f31610bdfe410450

darcs-hash:5706a21c079fc81d60dd47e522b7c5f8031bada9

always listen for ParameterStatus messages in message-case, since it seems to occur in a lot of contexts

darcs-hash:710ca4c709b378c0a969d5baa727b756da2de11e

darcs-hash:734722083f601e8175f226f88d5cae35257f0f66

darcs-hash:eed7f55d3df35a9991046bb9563ade84d1a22e76

darcs-hash:2ab86f88675866f7692efaa4551a2c47bd4867ec

darcs-hash:6e4c10161e0a3faebafba3f3be2bd692619abc80

darcs-hash:c8bf9ac4fdf150afe4a2dc242de0be21d218d42b

darcs-hash:711c818fc0fc42b85ee38d2aba635715c1e12805

darcs-hash:276606ffc44f3f733feb5e2d453a1a8f89f83dd9

darcs-hash:58656c715d3dcc2136a6bc1b92f1c83d73391bdf

darcs-hash:b570654ae6b0019f7c6fd9c155d3361310eef31b

darcs-hash:145d7a22afa7494842b4abba97b1b8fe694b0891

darcs-hash:e8929d768b25b08a41156d5c84f6866163911aaa

move s-sql:sql-ize to cl-postgres:to-sql-string, make exec-prepared accept any sql-stringifyable parameters

darcs-hash:9c738a3c74bf38c54d830ef19a6b98f18940f440

darcs-hash:20df1886d4fefba68e796311099dc8388fcfb75f