From jtv at xs4all.nl Sun Nov 20 15:30:24 2011 From: jtv at xs4all.nl (Jeroen Vermeulen) Date: Sun, 20 Nov 2011 22:30:24 +0700 Subject: [Libpqxx-packagers] Please test libpqxx 4.0 pre-release Message-ID: <4EC91D10.40004@xs4all.nl> Hello all, We're about to release a new version of libpqxx. As a subscriber to the libpqxx-packagers list you are getting advance warning; you'll probably want to test the new release on your systems. If any problems come up for your environment, where possible, we'd like to fix them upstream before release. The new version is called 4.0 and is scheduled to appear on 2011-11-27. Daily snapshots are available at: https://pqxx.org/~jtv/tmp/pqxx/ This is a major release, and many important things have changed. To start with, some big API changes: * Noticers are gone! The API relied on std::auto_ptr, which is deprecated. Noticers are replaced by a new class: errorhandler. * tablereader and tablewriter are gone. They weren't safe with multibyte encodings. * Prepared statements are now weakly-typed, and much simpler. It was mostly support for now-obsolete postgres versions that made them difficult. * There were too many nested classes in pqxx::result; fields and tuples are now stand-alone classes in the pqxx namespace. * In thread-safety metadata, "have_strerror_r" is now "have_safe_strerror." Visual C++ has a strerror_s(), so the name no longer fit. * For notify/listen, notify_listener has been replaced with notification_receiver. Notifications can have payload strings now. Many other things have changed: Visual C++ support has improved massively. Support for pre-8.0 versions of postgres has been dropped. The C++0x standard is now supported, as are gcc 4.6 and clang++. Binary strings are better, and postgres 9.0-style binary-escaping is supported where avaible. There's a new escaping-and-quoting function for SQL identifiers, called quote_name. Finally, the configure script now supports --enable-documentation and --disable-documentation, for faster or more complete builds. Please post to this list with any problems you may run into that can affect the upstream source tree or may be relevant to other package maintainers. Remember that the list is for people with other things to do, so please help keep chatter to a minimum. With thanks, Jeroen This process documented on: http://pqxx.org/development/libpqxx/wiki/PackageMaintainers Changes for this release: http://pqxx.org/development/libpqxx/browser/trunk/NEWS