Thread: psqlODBC 08.01.0100 Released

After a long development period, I'm pleased to announce the release of
version 08.01.0100 of psqlODBC, the PostgreSQL ODBC Driver.

This release represents a major change to the driver over previous versions;
in particular, the network code has been replaced with the PostgreSQL libpq
library. This allows us to more easily take advantage of updates and new
features that might be introduced to the PostgreSQL wire protocol, and also
allowed us to upgrade straight away to the version 3 protocol which was
previously unsupported. We were also able to add SSL support, as well as
Kerberos authentication support.

From this release, two versions of the driver are provided for Windows,
'PostgreSQL ANSI' which supports single and multibyte applications through
the ANSI ODBC API, and 'PostgreSQL Unicode' which provides Unicode support
through the Unicode ODBC API. On Unix systems, the driver type may be
selected via a configure option.

psqlODBC may be downloaded from http://www.postgresql.org/ftp/odbc/versions/
in source, Windows Installer, merge module, and basic zip file formats.

Please post any bug reports to the pgsql-odbc@postgresql.org mailing list.

I'd like to take this opportunity to thank all those involved with the
development, testing and bug fixing of the updated driver.

Dave Page
PostgreSQL Core Team

Dave Page wrote:
> From this release, two versions of the driver are provided for
> Windows, 'PostgreSQL ANSI' which supports single and multibyte
> applications through the ANSI ODBC API, and 'PostgreSQL Unicode'
> which provides Unicode support through the Unicode ODBC API. On Unix
> systems, the driver type may be selected via a configure option.

With my packager hat on, I'm puzzled by this.  I am now supposed to
produce two shared libraries?  I thought the idea was to have both sets
of functions in one binary and let the driver manager or application
program figure out which to call.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

On 9/11/05 8:28 pm, "Peter Eisentraut" <peter_e@gmx.net> wrote:

> Dave Page wrote:
>> From this release, two versions of the driver are provided for
>> Windows, 'PostgreSQL ANSI' which supports single and multibyte
>> applications through the ANSI ODBC API, and 'PostgreSQL Unicode'
>> which provides Unicode support through the Unicode ODBC API. On Unix
>> systems, the driver type may be selected via a configure option.
>
> With my packager hat on, I'm puzzled by this.  I am now supposed to
> produce two shared libraries?  I thought the idea was to have both sets
> of functions in one binary and let the driver manager or application
> program figure out which to call.

This was discussed in depth a few months back. The Unicode driver will only
work with Unicode data or non-unicode data that maps directly into the first
unicode page (or whatever the correct term is). Non-ASCII charsets don't
work correctly with the Unicode driver as a result.

Drivers such as the Microsoft SQL Server driver handle this by having an
option to map strings on the fly from the client encoding into unicode. It
has to be done this way because if the Unicode functions exist, the driver
manager will *always* map all function calls to those instead of the ANSI
versions.

To get around this without providing our own remapping of non-unicode data,
the driver was reverted back to the way it was in the 07.xx series - ie.
Having a Unicode and ANSI version on Windows. On Unix, the
--enable/disable-unicode option that you added some time back was
reinstated.

The net result of this change was that a whole heap of complaints from
people using latin* as their client encoding went away overnight.

I've made no secret of the fact that I know little of encoding issues
however, so if you have a better way to handle this then please speak up!

Regards, Dave

The version 2.70 of the BPM-/Worksystem OfficeTalk is released.
OfficeTalk supports the full integration of a PostgreSQL database as the base source and as the second source for the processes of your own.
An evaluation version is available, starting at 11/25/2006, from http://www.joops.com/OfficeTalk.zip.
For a datasheet or an evaluation version with base and second support of PostgreSQL, please contact the sender.

best regards,
Josef Springer
(Management)

	Address	Josef.Springer@joops.com	Orlando-di-Lasso Str. 2	D-85640 Putzbrunn
	Office	+49 (0)89 600 6920
	Fax	+49 (0)89 600 69220
	Web	http://www.joops.com

-- the software company --