summaryrefslogtreecommitdiff
path: root/databases/guile-pg
AgeCommit message (Collapse)AuthorFilesLines
2010-03-19Update to 0.39. Resolves type errors vs newer pgsql.gdt3-12/+13
(approval to update during freeze by agc@) - 0.39 | 2010-01-11 - Dropped (database postgres) procs - pg-lo-get-connection - pg-get-client-data - pg-set-client-data! These were pre-announced in Guile-PG 0.38 (2009-06-22) NEWS. - Proc `(database postgres) pg-parameter-status' no longer takes keyword This was pre-announced in Guile-PG 0.38 (2009-06-22) NEWS. - Maintenance uses autoconf 2.65, automake 1.11, libtool 2.2.6b - 0.38 | 2009-06-22 - Support for PostgreSQL 7.3 and earlier dropped Sorry, this was not pre-announced. Note that the subsequent version, i.e. PostgreSQL 7.4, was released 2003-11-17, over five years ago. - Dropped (database postgres) proc: pg-get-connection This was pre-announced in 0.37 (2008-05-24) NEWS. - External rep no longer includes "serial number" - Connection - Result These were pre-announced in 0.37 (2008-05-24) NEWS. - Planned retirement - pg-lo-get-connection - pg-get-client-data - pg-set-client-data! These (database postgres) procs provide or rely on associations that can better be expressed using normal Scheme facilities such as object properties, hash tables, etc, and thus are deemed a redundant maintenance burden; they WILL BE REMOVED by 2009-12-31. - Proc `(database postgres) pg-parameter-status' takes symbol `parm' These are equivalent: (pg-parameter-status CONN #:session_authorization) (pg-parameter-status CONN 'session_authorization) Note, however, that support for keyword `parm' is a misfeature, and WILL BE REMOVED by 2009-12-31. - Proc `(database postgres-qcons) sql-quote' more standards compliant Previously, this did single-quote escaping by inserting a backslash character prior to every single-quote. The result is acceptable by PostgreSQL, but is not standards compliant. Now, it does the escaping by doubling each single-quote, which is standards compliant and less prone to trigger warnings from the more recent PostgreSQL versions (8.2 and later). bef: (sql-quote "a'b") => "'a\\'b'" now: (sql-quote "a'b") => "'a''b'" - Changes to `pgtable-manager' (and thus `pgtable-worker') - Support for DEFAULT You can now use the keyword #:DEFAULT to specify DEFAULT as the value to insert into a table, or to update a column. Indeed, for column values, any keyword now expands to its name (sans `#:'). - #:insert-values no longer filters "serial" Previously, columns with "serial" type were filtered, so that it was possible to #:insert-values specifying only values for the other columns. Now, such usage raises a "column count mismatch" error; you must explicitly use #:DEFAULT. For example, given a table with column types "text", "serial", "text": bef: (W #:insert-values "foo" "bar") => ok now: (W #:insert-values "foo" "bar") => error (W #:insert-values "foo" #:DEFAULT "bar") => ok Although technically speaking the new behavior is incompatible, the previous behavior was never documented (secret misfeature), so the impact on your code is likely to be zero (no worries). - Connection object xrep omits "port" if "host" is a socket dir When the connection is Unix-domain (i.e., the "host" is a string that begins with slash that names a directory), the concept of "port" makes no sense. - Manual table-of-contents moved forward It used to be (strangely but perhaps following some outdated convention) at the end of the document. - New (database postgres) procs - pg-mblen While we wait for Guile to go multibyte (and stay there), this is a small building-block that eases "mostly ignorant" string processing. - pg-server-version This returns an integer representation of the server version of a connection, or `#f' if the connection is closed. - New (database postgres-resx) proc: object<-result This is useful for `SELECT EXPR;' where the result tuple consists of one row and one column. - Maintenance uses autoconf 2.63, automake 1.11, libtool 2.2.6
2010-02-10Bump revision for change of PostgreSQL default version.joerg1-2/+2
2010-01-29DESTDIR supportjoerg1-3/+5
2009-12-15Recursive bump for libltdljoerg1-2/+2
2009-06-14Remove @dirrm entries from PLISTsjoerg1-4/+1
2009-05-20Recursive ABI depends update and PKGREVISION bump for readline-6.0 shlibwiz1-1/+2
major change. Reported by Robert Elz in PR 41345.
2009-05-19Use standard location for LICENSE line (in MAINTAINER/HOMEPAGE/COMMENTwiz1-2/+2
block). Uncomment some commented out LICENSE lines while here.
2008-10-20Update to 0.37. Headlines from NEWS:gdt2-7/+6
- 0.37 | 2008-05-24 - Configuration change: search $prefix for PostgreSQL headers/libs - Change to pg-get-connection This proc now returns #f if its arg's connection is no longer live. You should probably avoid it altogether; see following NEWS item. - Planned modesty Currently, Guile-PG exposes some accounting (implementation) details that it shouldn't. These are the "serial number" of connection and result objects, and the link between a result object the connection object where it originated. These details WILL BE REMOVED after 2008-10-01; do NOT rely on them. Practically speaking, this means `pg-get-connection' will be deleted and the external representation for the objects will drop the "N" field: until 2008-10-01: #<PG-CONN:N:...> and #<PG-RESULT:N:...> after 2008-10-01: #<PG-CONN:...> and #<PG-RESULT:...> - Tests issue SQL commands directly to CREATE and DROP the test database Previously "make check" required the commands createdb(1) and dropdb(1) (or destroydb(1) for older PostgreSQL versions) to be installed on the system. Now, the test infrastructure uses Guile-PG module (database postgres) to connect to "template1" and issues SQL commands "CREATE DATABASE" and "DROP DATABASE" directly. - New (database postgres-meta) proc: information-schema-names - New (database postgres-meta) proc: information-schema-coldefs These procs describe Guile-PG's "standard introspection" support, as specified in the PostgreSQL 7.4.19 documentation (chapter 32, "The Information Schema"). Additionally, loading the module defines type converters for `cardinal_number', `character_data' and `sql_identifier'. The `time_stamp' type converter does not seem to be used and is not provided. - New pgtable-manager (and -worker) command: #:finish This closes the (internal) connection and arranges for all future invocations of the closure to signal a "dead connection" error. - Proc `gxrepl' closes connection when done - New support for #:FOO-all combiners in `parse+make-SELECT-tree' This (database postgres-qcons) proc now supports #:union-all, #:intersect-all and #:except-all, as combiners. - Maintenance uses autoconf 2.62, automake 1.10.1, libtool 2.2.2
2008-03-13Make PostgreSQL 8.2 the default version. Bump all packages using it.joerg1-1/+2
Remove PostgreSQL 8.0 as choice.
2008-03-03Update to 0.36. Changes: be more careful in test code not to usegdt2-6/+6
features that are not always available.
2008-02-16Update to 0.35.gdt2-6/+6
- 0.35 | 2008-02-13 - Bugfix: composition INTERSECT in `parse+make-SELECT-tree' This proc, in module (database postgres-qcons), used to erroneously accept #:intersection and emit "INTERSECTION". Now, it accepts #:intersect and emits "INTERSECT". - New (database postgres) procs - pg-escape-string-conn - pg-escape-bytea-conn - pg-unescape-bytea - Tested against PostgreSQL 7.4.19
2008-01-05Add commented out LICENSE line.wiz1-1/+2
2008-01-05Update to 0.34.gdt2-7/+6
Highlights from NEWS: - 0.34 | 2007-12-13 - License now GPLv3+ (see COPYING) - New (database postgres) procs - pg-finish - pg-flush - Tested against PostgreSQL 7.4.18 - 0.33 | 2007-05-20 - New type converters in module (database postgres-types) int decimal numeric varchar character bytea - New support for special constructs in (database postgres-qcons) (in/set A B...) => A IN ( B, ... ) (between A B C) => ( A BETWEEN B AND C ) (any--OP A B) => ( A OP ANY B ) (all--OP A B) => ( A OP ALL B ) For the latter two, OP is a comparison operator, e.g `='. Parentheses and commas are added automatically. - 0.32 | 2007-04-11 - New command for `pgtable-manager': #:tuples-result->rows This uses `(database postgres-resx) result->object-rows'. For example: (define T (pgtable-worker ...)) (define R (T #:select ...)) (equal? (T #:tuples-result->rows R) (map (lambda (x) (map cdr x)) (T #:tuples-result->alists R))) => #t - 0.31 | 2007-04-03 - Opaque string support removed Opaque string support in modules (database postgres-table) and (database postgres-qcons) has been removed. This was announced in NEWS below for Guile-PG 0.30 (2006-04-04). - Support for `pgtable-manager' "data commands" removed Announced in NEWS below for Guile-PG 0.30 (2006-04-04). - 0.30 | 2006-04-04 - New stuff for `pgtable-manager' (and by extension `pgtable-worker') - Support for NULL You can now use the keyword #:NULL to specify NULL as the value to insert into a table, or to update a column. - New command: #:update-col-alist This is like #:update-col, except that the COLS and DATA are specified as a single alist arg, not separately. - New (database postgres) procs The following procs are associated with the `PQPROTOCOLVERSION' feature in the `pg-guile-pg-loaded' return value. Note that this is in contrast to the one-to-one correspondance between feature and libpq function for previous Guile-PG releases. - pg-protocol-version - pg-transaction-status - pg-parameter-status - pg-set-error-verbosity - pg-result-error-field - pg-ftable - pg-ftablecol - pg-fformat These adhere closely to the C functions in the libpq interface. Here is a table listing the functions and their behavior for installations prior to PostgreSQL 7.4. libpq func behavior: do nothing and return PQprotocolVersion 2 PQtransactionStatus #:unknown PQparameterStatus #f PQsetErrorVerbosity #:default PQresultErrorField #f PQftable #f PQftablecol #f PQfformat #f - pg-put-copy-data - pg-put-copy-end - pg-get-copy-data These have a simplified, "more Schemey", interface. They cannot be used when connected to a "Protocol 2.0" (PostgreSQL 7.3.x and prior) server. - pg-exec-params - pg-exec-prepared - pg-send-query-params - pg-send-query-prepared These have a simplified, "more Schemey", interface, and some serious (though provisionary) restrictions. They cannot be used when connected to a "Protocol 2.0" (PostgreSQL 7.3.x and prior) server. See new section "Parameters" in the manual for details.
2008-01-05Fix link to database code to be from guile16. PKGREVISION++.gdt2-6/+8
2007-06-12Point at lang/guile16 instead of lang/guile in preparation for updatingdmcmahill1-3/+3
lang/guile to 1.8.1 from 1.6.8. These pkgs seemed to fail to build with guile 1.8.1, but maybe can be easily fixed.
2007-04-02Upstream MASTER_SITES, HOMEPAGE have changed.gdt1-3/+3
s;www.glug.org/people/ttn;www.gnuvola.org/g
2006-12-28I see no reason to force PostgreSQL 7.4 here, so remove the forcedjoerg1-4/+2
version and bump revision.
2006-03-30* Honor PKGINFODIR.jlam2-4/+4
* List the info files directly in the PLIST.
2006-02-05Recursive revision bump / recommended bump for gettext ABI change.joerg1-1/+2
2005-12-09Update to 0.29. Changes since last update:gdt4-30/+10
- 0.29 | 2005-08-25 - Dropped proc: where-clausifier - Dropped proc: tuples-result->table - For `gxrepl', results are now printed with " | " field separator - All (database postgres) procs now tested - Support files guile.m4 and modsup.h synched with Guile 1.4.1.106 - 0.28 | 2005-05-09 - Bugfix: array reference handling in (database postgres-qcons) - FSF street address updated in copyright notices - 0.27 | 2005-03-02 - Result objects print without redundant "PGRES_" prefix - New command for (database postgres-table) proc `pgtable-manager' - New (database postgres-resx) proc: result->object-rows - Changes to module (database postgres-qcons) - 0.26 | 2005-02-24 - Expiration date set for opaque string support - Expiration date set for two (database postegres-table) procs - Dropped (database postgres-types) proc: dbcoltype:name - New type converters in module (database postgres-types) - New module: (database postgres-qcons) - New module: (database postgres-resdisp) - New module: (database postgres-gxrepl) - 0.25 | 2005-01-02 - New (database postgres) proc: pg-result-error-message - 0.24 | 2004-11-24 - New (database postgres) proc: pg-set-nonblocking! - New (database postgres) proc: pg-is-nonblocking?
2005-08-10Change my email address to @NetBSD.org.gdt1-2/+2
2005-05-22Remove USE_GNU_TOOLS and replace with the correct USE_TOOLS definitions:jlam1-2/+2
USE_GNU_TOOLS -> USE_TOOLS awk -> gawk m4 -> gm4 make -> gmake sed -> gsed yacc -> bison
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-02-23Add RMD160 digests in addition to SHA1 ones.agc1-1/+2
2004-12-22Remove hack, now that pg_config comes with postgresql-libs package.wiz1-4/+1
2004-12-03Update to 0.23. Provided by Greg Troxel in pkgsrc-wip.wiz9-86/+68
Uses guile-1.6 and postgresql-7.4. Four years of development since the previous version: many changes. XXX: This package includes a hack since pgsql.bl3.mk does not provide a way to get the matching -clients package.
2004-10-15Update linkage to libltdl (via guile{,14}), which is now its own package.tv1-2/+2
Unfortunately, guile{,14}/buildlink3.mk directly includes it, and I don't know which dependencies actually need libltdl, so it was a recursive bump. Hopefully this recursive inclusion can be ripped out of guile{,14}/buildlink3.mk at some point and bubble down to dependencies that actually use libltdl, avoiding this headache in the future....
2004-10-03Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10tv1-2/+2
in the process. (More information on tech-pkg.) Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and installing .la files. Bump PKGREVISION (only) of all packages depending directly on the above via a buildlink3 include.
2004-09-22Mechanical changes to package PLISTs to make use of LIBTOOLIZE_PLIST.jlam1-3/+1
All library names listed by *.la files no longer need to be listed in the PLIST, e.g., instead of: lib/libfoo.a lib/libfoo.la lib/libfoo.so lib/libfoo.so.0 lib/libfoo.so.0.1 one simply needs: lib/libfoo.la and bsd.pkg.mk will automatically ensure that the additional library names are listed in the installed package +CONTENTS file. Also make LIBTOOLIZE_PLIST default to "yes".
2004-08-13Set PGSQL_VERSION_REQD to 73 (for now) to fix the build.recht1-1/+3
2004-07-24Use the new mk/pgsql.buildlink3.mk to select the correct PostgreSQLrecht1-5/+3
version.
2004-05-03Convert to buildlink3.wiz1-4/+4
2004-03-26PKGREVISION bump after openssl-security-fix-update to 0.9.6m.wiz1-2/+2
Buildlink files: RECOMMENDED version changed to current version.
2004-02-14LIBTOOL_OVERRIDE and SHLIBTOOL_OVERRIDE are now lists of shell globsjlam1-2/+1
relative to ${WRKSRC}. Remove redundant LIBTOOL_OVERRIDE settings that are automatically handled by the default setting in bsd.pkg.mk.
2004-01-22replace deprecated USE_GMAKE with USE_GNU_TOOLS+=make.grant1-2/+2
2004-01-20Remove info files entries from PLIST files.seb1-2/+1
2003-08-09USE_NEW_TEXINFO is unnecessary now.seb1-2/+1
2003-07-17s/netbsd.org/NetBSD.org/grant1-2/+2
2003-07-13PKGREVISION bump for libiconv update.wiz1-2/+2
2003-06-29Convert to USE_NEW_TEXINFO.seb5-7/+33
Fix the Info directory file entry and provide patches for both the .texi and the .info file so USE_MAKEINFO is not needed.
2003-06-05Bump revisions following the guile14's threaded fix.uebayasi1-2/+2
2003-01-07Use the right interface of Buildlinked directory.uebayasi1-2/+2
Pointed out by wiz.
2003-01-07Buildlinkify.uebayasi1-2/+4
2003-01-07Rename older (<1.6) Guile as guile14.uebayasi1-2/+2
Packages using Guile now all depend on guile14. These packages are expected to be made depend on newer Guile (1.6.x) when updated in the future.
2003-01-05Bump PKGREVISION due to increase in the major number of libpq.so betweenjlam1-3/+4
version 7.2.3 and 7.3.1 of databases/postgresql-lib.
2002-10-27Imported guile-pg:cjones7-0/+84
Guile-pg is a Guile module providing access and allowing updates to PostgreSQL databases from Guile scripts. Guile is the GNU interpreter for the Scheme language and PostgreSQL is a free relational database management system.