awful-postgresql

  1. awful-postgresql
    1. Description
    2. Author
    3. Requirements
    4. Procedures
      1. enable-db
      2. switch-to-postgresql-database
    5. Parameters
      1. db-result-processor
    6. License
    7. Version history
      1. version 0.6.0
      2. version 0.5.1
      3. version 0.5
      4. version 0.4
      5. version 0.3
      6. version 0.2
      7. version 0.1

Description

Postgresql support for awful.

This extension provides the enable-db and switch-to-postgresql-database procedures which add Postgresql support for awful, based on the features provided by the postgresql egg.

Author

Mario Domenech Goulart

Requirements

Procedures

enable-db

[procedure] (enable-db)

Enable Postgresql support for awful. This procedure basically sets up awful to use the connection, disconnection, query and query escaping procedures for Postgresql databases.

switch-to-postgresql-database

[procedure] (switch-to-postgresql-database)

Resets all the awful db-related parameters to postgresql values (for when using multiple databases under the same awful server).

Parameters

db-result-processor

This parameter yields a one-argument procedure (the argument is the object representing the results as returned by the postgresql bindings).

The default value is:

(lambda (result)
  (row-map identity result))

This parameter has been added in version 0.5.

License

Copyright (c) 2008-2011, Mario Domenech Goulart
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:

Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.

Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.

Neither the name of the author nor the names of its contributors may
be used to endorse or promote products derived from this software
without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
OF THE POSSIBILITY OF SUCH DAMAGE.

Version history

version 0.6.0

In case of an empty result set from a query, (db-inquirer) will now return '() instead of #f.

This change can be specially harmful in case you have something like

(or ($db "some query") "something")

In this example, if the query returns an empty result set, that expression would produce:

version 0.5.1
version 0.5
version 0.4
version 0.3
version 0.2
version 0.1