CXXFLAGS, and LDFLAGS by the buildlink.mk files so remove the extra
definitions to add them from the package Makefiles. As advised by the
bsd.buildlink.mk file, also ensure that the buildlink.mk files are
included prior to defining any package-specific CFLAGS/LDFLAGS to ensure
that the buildlink directories are at the head of the compiler search
paths.
Fixed that altering ShowErrorStatement also altered AutoCommit!
Fixed DBD::Proxy to handle commit() and rollback(). Long overdue, sorry.
Fixed incompatibility with perl 5.004 (but no one's using that right? :)
Fixed connect_cached and prepare_cached to not be affected by the order
of elements in the attribute hash.
Fixed version number of DBI::Shell
Defined and documented table_info() attribute semantics (ODBC compatible)
linked from a particular package, and add a pre-configure target to
the buildlink.mk file to more painlessly use buildlink.mk files. A
${BUILDLINK_TARGETS} variable still exists in case a package _must_
define NO_CONFIGURE.
Reimplemented fetchrow_hashref in C, now fetches about 25% faster!
Changed behaviour if both PrintError and RaiseError are enabled
to simply do both (in that order, obviously :)
Slight reduction in DBI handle creation overhead
Fixed $dbh->{Driver} & $sth->{Database} to return 'outer' handles.
Fixed execute param count check to honour RaiseError
Fixed build for perl5.6.1 with PERLIO
Fixed client sql restrictions in ProxyServer.pm
Fixed batch mode command parsing in Shell
Fixed typo in selectcol_arrayref docs
Fixed selectrow_hashref to be available to callers
Fixed core dump if statement handle didn't define Statement attribute
Added bind_param_inout docs to DBI::DBD
Added note to data_sources() method docs that some drivers may
require a connected database handle to be supplied as an attribute
Trace of install_driver method now shows path of driver file loaded
Changed many '||' to 'or' in the docs
Updated DBD::ADO again (improvements in error handling)
Updated Win32::DBIODBC (Win32::ODBC emulation)
Updated email and web addresses in DBI::FAQ
- SearchBuilder.pm - refactored to allow LEFT joins.
- SearchBuilder::Record::Cachable now constructs cache keys in a way
that doesn't lose when records in different tables have the same keys.
- Added DBIx::SearchBuilder::Record::Cachable from <mhat@netlag.com>
- Changed SearchBuilder->Count to do the right thing if no
query has been performed
postgresql sources:
postgresql-client, postgresql-docs, postgresql-lib, postgresql-server,
postgresql-plperl, postgresql-pltcl,
odbc-postgresql, py-postgresql, tcl-postgresql, tk-postgresql
to 7.1.2 or to depend on postgresql-libs-7.1.2. Changes from version 7.1.1:
Fix PL/PgSQL SELECTs when returning no rows
Fix for psql backslash core dump
Referential integrity permission fix
Optimizer fixes
pg_dump cleanups
- fix segmentation fault in pg_error
- bug-fix for core-dump after any failed function call
- add support for the datatype bytea
- fix bug in connect method, which erroneously set the userid and the
password to the environment variables DBI_USER and DBI_PASS
- which removed the special handling of a backslash when used for octal
presentation. Now a backslash always will be escaped.
- remove memory-leak in ping function, bug-fix
- correct the recognition of primary keys in table_attributes().
- fix a segmentation fault in DBD::pg::blob_read() when reading LOBs that
required perl to reallocate space for the variable holding the scalar value
- updated test.pl to create a test blob larger than 256 bytes (now 128 Kbytes)
- fix a seg-fault when inserting large amounts of text.
- remove the newlines from the error messages and quote date placeholders.
Use BUILDLINK_INCDIR, BUILDLINK_LIBDIR for locations of linked headers
and libraries. Create a variable BUILDLINK_TARGETS whose value is the
list of build-link targets to execute.
databases prior to installing a new version of PostgreSQL from PRE-INSTALL
time to DEINSTALL time. Remove ${CAT} from the INSTALL file as it's no
longer needed in the script.
start_precmd in the pgsql rc.d script. This is more correct, since if
postgresql-server is installed but never used, then no database really
needs to be initialized. As a side-effect, the bulk-builds of postgresql
should now leave less crud in the aftermath of deinstalling postgresql.
