2.7.0

The COPY FROM/COPY TO API that Pgsql uses is obsolete and deprecated.

This changes it to use the new API in libpq.

Also, added $handle copy_complete which terminates a COPY FROM stdin operation without the hack of writing {\.} to the handle.

Finally, updated tests and added tests for COPY.

2.6.3

Allow pg_exec to handle SQL statements starting with a comment.

v2.6.2: use name transactions (savepoints) for sqlite transactions

• Use named transactions (savepoints) for sqlite transactions to allow the import of postgres results using pg_sqlite to occur within an outer sqlite transaction.
• When doing pg_select, etc, with -variables, distinguish between "::type" which is a cast and ":::type" which is a reference to a glocal Tcl variable named "type".
• Fix use-after-free when disconnecting inside pg_select body.
• Add travis build status icon to readme.
• Bump version to 2.6.2.

2.6.1

• Update handling of Tcl Objects in pgtclSqlite.c to fix memory leak.
• Add tests for pg_sqlite command in tests/sqlite.test
• Slightly change format of handle name to not use socket id since that's not guaranteed stable.

v2.6.0

This release drops compatibility with Tcl 8.3 and earlier!

Previous releases will not be compatible with Tcl 8.7 and later!

• Minor bug fix (crash in pg_sqlite db info -db with no argument to -db).
• Remove compatibility with Tcl 8.3 as per TIP-503

v2.5.1

Roll back the change in the return value from pg_select - it was undefined but there is code that depends on the final command in the final loop of the block being retained.

v2.5.0

• Added -count varname to pg_select, to make the number of rows requested visible inside the loop.
• Added -max colname varname to pg_sqlite import_postgres_result, to track latest-timestamp changes on the fly.

v2.4.0

Re-arrange the include file layout and library installation to allow connection management code in pgtclId.c to be found by cmake and called by c and c++ applications.

v2.3.4

Clean up calling sequence for PgSetResultId to correctly flag an error when the hard limit on number of result handles is reached. See Issue #21

v2.3.3

Handle "integers" imported from PostgreSQL boolean types.

Changed: in "pg_sqlite import_postgres_result" textual boolean values are legal integers

Because an int sqlite column might be mapped from a boolean postgresql column, so t,'true','on',and so on are imported as integer 1.