pgpool is a connection server for PostgreSQL. pgpool runs between
PostgreSQL's clients(front ends) and servers(back ends). A PostgreSQL
client can connect to pgpool as if it were a standard PostgreSQL
server.
pgpool caches the connection to PostgreSQL server to reduce the
overhead to establish the connection to it. Also, pgpool could use
two PostgreSQL servers for fail over. If the first server goes down,
pgpool will automatically switch to the secondary server. Moreover,
pgpool supports scheduled switch over.
within NetBSD-current's bsd.own.mk, which conflicts with its usage in
pkgsrc. The package that use USE_PAM have been converted to use the
bsd.options.mk framework. This should fix PR pkg/29257.
for those wishing to migrate data from any previous release.
Major changes relative to 7.4.x:
* Savepoints
* Point-in-Time recovery
* Tablespaces
* Improved buffer management
* ALTER TABLE column management improvements
Full list of changes is available at:
http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0
Also note that PostgreSQL server listens also on localhost (127.0.0.1)
by default now.
Changes
* Disallow "LOAD" to non-superusers
On platforms that will automatically execute initialization
functions of a shared library (this includes at least Windows and
ELF-based Unixen), "LOAD" can be used to make the server execute
arbitrary code. Thanks to NGS Software for reporting this.
* Check that creator of an aggregate function has the right to
execute the specified transition functions
This oversight made it possible to bypass denial of EXECUTE
permission on a function.
* Fix security and 64-bit issues in contrib/intagg
* Add needed STRICT marking to some contrib functions (Kris Jurka)
* Avoid buffer overrun when plpgsql cursor declaration has too many
parameters (Neil)
* Fix planning error for FULL and RIGHT outer joins
The result of the join was mistakenly supposed to be sorted the
same as the left input. This could not only deliver mis-sorted
output to the user, but in case of nested merge joins could give
outright wrong answers.
* Fix plperl for quote marks in tuple fields
* Fix display of negative intervals in SQL and GERMAN datestyles
* Make age(timestamptz) do calculation in local timezone not GMT
from 7.3.8, including several security-related issues. A dump/restore
is not required for those running 7.3.X.
Changes
* Disallow "LOAD" to non-superusers
On platforms that will automatically execute initialization
functions of a shared library (this includes at least Windows and
ELF-based Unixen), "LOAD" can be used to make the server execute
arbitrary code. Thanks to NGS Software for reporting this.
* Check that creator of an aggregate function has the right to
execute the specified transition functions
This oversight made it possible to bypass denial of EXECUTE
permission on a function.
* Fix security and 64-bit issues in contrib/intagg
* Add needed STRICT marking to some contrib functions (Kris Jurka)
* Avoid buffer overrun when plpgsql cursor declaration has too many
parameters (Neil)
* Fix planning error for FULL and RIGHT outer joins
The result of the join was mistakenly supposed to be sorted the
same as the left input. This could not only deliver mis-sorted
output to the user, but in case of nested merge joins could give
outright wrong answers.
* Fix plperl for quote marks in tuple fields
* Fix display of negative intervals in SQL and GERMAN datestyles
- ok'ed wulf@
> GeneWeb version 4.10
> --------------------
>
> * Languages
> - [29 Jan 04] Added "Breton" (Tepod Gwilhmod, Gwenael Emelyanoff,
> Bertrand Yeurc'h).
>
> * GeneWeb server or CGI (gwd)
> - [06 Nov 04] In statistics, added displaying of oldest couples perhaps
> still alive and engaged.
> - [06 Jan 04] Fixed bug: when changing a child's name using "change
> children's names", the possible image was not renamed, causing
> its disparition.
> - [05 Jan 04] Added database configuration variable "show_consang":
> when set to "no" the possible consanguinity is not displayed in
> personal pages. Added also variable "fast_alphabetic": when set
> to "yes", the alphabetic display of surnames or first names is fast
> but the number of surnames of fist names is not displayed (interesting
> for large databases).
> - [04 Dec 03] Fixed bug: in case of two wizards make changes at
> the same time, there were (rare) cases where one of the changes
> erases the other one (instead of being rejected by the message
> "database is locked").
> - [29 Nov 03] Added optional "border" and "background color" for
> trees displaying (relationship links, ancestors and descendants).
> - [28 Nov 03] Fixed bug creating sometimes dates with null month
> (and not null day) resulting problems with "gwu-gwc" and "cleaning
> up" the database by gwsetup (happened when a date was entered
> with month=13 which was erroneously not rejected).
> - [18 Jan 03] Added a system of black list for the database forum;
> the environment variable "forum_exclude_file" can be set to a
> file name containing a list of excluded IP addresses which cannot
> post. In the lines of this file, the joker character "*" can be
> used to specify any string (e.g. "*" exclude everybody).
> - [14 Jan 03] In form to add message in the database forum, added
> buttons "private/public": only "wizards" and "friend" can see
> "private" messages.
> - [06 Jan 03] In welcome page, added wizard's name (when named).
>
> * Base configuration files (base.gwf)
> - [19 Mar 03] Added a variable "moved" to indicate that the database
> has been moved. This displays the new template file "moved.txt".
>
> * Setup program (gwsetup)
> - [12 Nov 03] Fixed bug: the links to the documentation did not work
> with modern browsers.
>
> * GeneWeb uncompiler (gwu)
> - [12 Feb 03] Fixed bug: exporting bad format when places containing
> just spaces.
> "private" messages.
> - [06 Jan 03] In welcome page, added wizard's name (when named).
>
> * Base configuration files (base.gwf)
> - [19 Mar 03] Added a variable "moved" to indicate that the database
> has been moved. This displays the new template file "moved.txt".
>
> * Setup program (gwsetup)
> - [12 Nov 03] Fixed bug: the links to the documentation did not work
> with modern browsers.
>
> * GeneWeb uncompiler (gwu)
> - [12 Feb 03] Fixed bug: exporting bad format when places containing
> just spaces.
> - [11 Feb 03] Added option -maxlev to specify a maximum number of
> generations (descendants only) to export.
>
> * GeneWeb databases Transfer Program (gwtp)
> - [08 Dec 03] Added German (Falko Trojahn).
> - [14 Oct 03] Added Spanish (Luis Mondesi).
> - [03 Jan 03] Fixed bug: when wizard notes, the "send database" did
> not work.
python*-pth packages into meta-packages which will install the non-pth
packages. Bump PKGREVISIONs on the non-pth versions to propagate the
thread change, but leave the *-pth versions untouched to not affect
existing installations.
Sync all PYTHON_VERSIONS_AFFECTED lines in package Makefiles.
This is basically bug fix release, but official changes aren't provided
yet. Please refer ChangeLog.
Here is pkgsrc changes:
o Set RUBY_HAS_ARCHLIB=yes for Ruby packages including archtecture depending
extention library in order to depend more specific Ruby.
o Now install database for ri(1). Fix PR pkg/28566.
o Net::IMAP
* lib/net/imap.rb (u8tou16): fixed typo. fixed: [ruby-list:40546]
o NKF:
* ext/nkf/nkf-utf8/nkf.c (reinit): should initialize all static
variables. fixed: [ruby-list:40445]
* ext/nkf/lib/kconv.rb (Kconv::RegexpEucjp): second byte is up to
0xfe.
* ext/nkf/lib/kconv.rb (Kconv#kconv): should handle UTF8 and UTF16
properly.
o WEBrick
* lib/webrick/httpauth/htpasswd.rb (WEBrick::Htpasswd#reload):
raise NotImplementedError if password is encrypted by digest
algorithms. This patch is contributed by sheepman. [ruby-list:40467]
* lib/webrick/httpauth/digestauth.rb
(WEBrick::HTTPAuth::DigestAuth#_authenticate): fix digest calculation.
This patch is contributed by sheepman. [ruby-list:40482]
* lib/webrick/{httpauth.rb,httpauth/basicauth.rb,httpproxy.rb}: use
pack/unpack-template char "m" instead of lib/base64.rb to do base64
encoding/decoding. fixed: [ruby-dev:25336]
Changes since 1.12:
- NEW: jdb added to the freebsd ports tree
maintainer: larse@isi.edu
- BUG FIX: properly handle trailing spaces when data must be numeric
(ex. dbstats with -FS, see test dbstats_trailing_spaces)
Fix from Ning Xu .
- NEW: dbcolize error message improved (bug report from Terrence
Brannon), and list format documented in the README.
- NEW: cgi_to_db convergs CGI.pm-format storage to jdb list format
- BUG FIX: handle numeric synonyms for column names in dbcol properly
- ENHANCEMENT: "talking about columns" section added to README.
Lack of documentation pointed out by Lars Eggert.
- CHANGE: dbformmail now defaults to using Mail ("Berkeley Mail")
to send mail, rather than sendmail (sendmail is still an option,
but mail doesn't require running as root)
- NEW: on platforms that support it (i.e., with perl 5.8), jdb works
fine with unicode
- NEW: dbfilevalidate: check a db file for some common errors
Functionality added or changed:
* The Mac OS X 10.3 installation disk images now include a MySQL
Preference Pane for the Mac OS X Control Panel that enables the user
to start and stop the MySQL server via the GUI and activate and
deactivate the automatic MySQL server startup on bootup.
* Seconds_Behind_Master will be NULL (which means ``unknown'')
if the slave SQL thread is not running, or if the slave I/O thread
is not running or not connected to master. It will be zero if the
SQL thread has caught up with the I/O thread. It no longer grows
indefinitely if the master is idle.
* InnoDB: Do not acquire an internal InnoDB table lock in LOCK
TABLES if AUTOCOMMIT=1. This helps in porting old MyISAM applications
to InnoDB. InnoDB table locks in that case caused deadlocks very easily.
* InnoDB: Print a more descriptive error and refuse to start InnoDB
if the size of `ibdata' files is smaller than what is stored in the
tablespace header; innodb_force_recovery overrides this.
* The MySQL server aborts immediately instead of simply issuing a
warning if it is started with the --log-bin option but cannot
initialize the binary log at startup (that is, an error occurs when
writing to the binary log file or binary log index file).
* The binary log file and binary log index file now behave like
MyISAM when there is a "disk full" or "quota exceeded" error. See
section A.4.3 How MySQL Handles a Full Disk.
Many bugfixes were fixed... see
http://dev.mysql.com/doc/mysql/en/News-4.1.9.html
with sqlite version 2 (everything in this package ends in `3'). DESCR:
SQLite is a C library that implements an SQL database engine. Programs
that link with the SQLite library can have SQL database access without
running a separate RDBMS process. The distribution comes with a standalone
command-line access program (sqlite) that can be used to administer an
SQLite database and which serves as an example of how to use the SQLite
library.
SQLite is not a client library used to connect to a big database server.
SQLite is the server. The SQLite library reads and writes directly to and
from the database files on disk.
It includes the correct buildlink3.mk file from either Linux-PAM
(security/PAM) or OpenPAM (security/openpam) and eventually will
support solaris-pam. pam.buildlink3.mk will:
* set PAMBASE to the base directory of the PAM files;
* set PAM_TYPE to the PAM implementation used.
There are two variables that can be used to tweak the selection of
the PAM implementation:
PAM_DEFAULT is a user-settable variable whose value is the default
PAM implementation to use.
PAM_ACCEPTED is a package-settable list of PAM implementations
that may be used by the package.
Modify most packages that include PAM/buildlink3.mk to include
pam.buildlink3.mk instead.
Note: This fix the build with latest db4 package.
Package changes:
Remove references to LOCALBASE.
Add test target support.
Changes since last packaged version (4.2.4):
4.3.0:
* Added support for building properly against BerkeleyDB 4.3.21.
* fixed bug introduced in 4.2.8 that prevent the module from
compiling against BerkeleyDB 3.2 (which doesn't support pget).
* setup.py was cleaned up a bit to search for and find the latest
version of the correct combo of db.h and libdb.
4.2.9:
* DB keys() values() and items() methods were ignoring their optional
txn parameter. This would lead to deadlocks in applications
needing those to be transaction protected.
4.2.8:
* Adds support for DB and DBCursor pget methods. Based on a patch
submitted to the mailing list by Ian Ward <ian@arevco.ca>
* Added weakref support to all bsddb.db objects.
* Make DBTxn objects automatically call abort() in their destructor if
not yet finalized and raise a RuntimeWarning to that effect.
4.2.7:
* fix an error with the legacy interface relying on the DB_TRUNCATE
flag that changed behaviour to not work in a locking environment
with BerkeleyDB 4.2.52. [SF bug id 897820]
* fixed memory leaks in DB.get, DBC.set_range and potentially several
other methods that would occur primarily when using queue | recno
format databases with integer keys. [SF patch id 967763]
4.2.6:
* the DB.has_key method was not honoring its txn parameter to perform
its lookup within the specified (optional) transaction. fixed.
[SF bug id 914019]
4.2.5:
* Fixed a bug in the compatibility interface set_location() method
where it would not properly search to the next nearest key when
used on BTree databases. [SF bug id 788421]
* Fixed a bug in the compatibility interface set_location() method
where it could crash when looking up keys in a hash or recno
format database due to an incorrect free().
configure script still used -pthread during the POSIX mutex test even
when we explicitly disabled pthread through CONFIGURE_ENV, resulting
in re-enabling pthread.
Bump PKGREVISION.
under share/examples/rc.d. The variable name already was named
RCD_SCRIPTS_EXAMPLEDIR.
This is from ideas from Greg Woods and others.
Also bumped PKGREVISION for all packages using RCD_SCRIPTS mechanism
(as requested by wiz).
* Automatic initialization of replication clients
* Replication election process is now Paxos compliant
* In memory transaction logs allowing in memory databases
* Enhanced Java API nearly identical to that of our Java Edition
* Native support for sequence number generation
* Degree 2 transaction isolation
* Mutex statistics can now be easily gathered and recorded
* Support for Itanium2 chips running Windows XP
PyTable is a relational database wrapper based on BasicProperty's rich
property-based modeling system. PyTable provides a "thick" wrapper for
PostgreSQL (and MySQL) database adapters which fills in missing functionality
in the adapter layer to provide a uniform rich external API.
Description:
Class::DBI provides a convenient abstraction layer to a database.
It not only provides a simple database to object mapping layer, but can
be used to implement several higher order database functions (triggers,
referential integrity, cascading delete etc.), at the application level,
rather than at the database.
This is particularly useful when using a database which doesn't support
these (such as MySQL), or when you would like your code to be portable
across multiple databases which might implement these things in
different ways.
In short, Class::DBI aims to make it simple to introduce 'best practice'
when dealing with data stored in a relational database.
Description:
This module was inspired by the excellent the DBIx::Abstract manpage.
However, in using that module I found that what I really wanted to do
was generate SQL, but still retain complete control over my statement
handles and use the DBI interface. So, I set out to create an abstract
SQL generation module.
module directory has changed (eg. "darwin-2level" vs.
"darwin-thread-multi-2level").
binary packages of perl modules need to be distinguishable between
being built against threaded perl and unthreaded perl, so bump the
PKGREVISION of all perl module packages and introduce
BUILDLINK_RECOMMENDED for perl as perl>=5.8.5nb5 so the correct
dependencies are registered and the binary packages are distinct.
addresses PR pkg/28619 from H. Todd Fujinaka.
PostgreSQL configure/build infrastructure tries very hard to separate
rpath flags from other LDFLAGS, which is completely unnecessary in
pkgsrc since the wrapper scripts are smart enough to deal with it on
their own. In this case, the GNU configure script was stripping out
the rpath to libperl.so when setting perl_embed_ldflags, so modify
the configure script to not do this.
Also re-enable this package since it's possible to load the plperl.so
language module again. I tested this with:
createdb foo
createlang -d foo plperl
only pass only the -L* LDFLAGS to the linker. This is correct for
pkgsrc since the wrapper scripts take care of correctly passing the
rpath info to the linker, so we don't need to filter those out. This
allows plpgsql.so to find libintl.so if we are using the pkgsrc version
of it. Bump the PKGREVISION of postgresql*-lib to 7.3.8nb1 and
7.4.6nb2.
Link the postgres binary with the necessary flags to allow it to
dlopen() modules that use pthreads[*]. This should allow postgres to
open a plperl.so module built on a system with perl+threads. Bump
the PKGREVISION of postgresql*-server to 7.3.8nb2 and 7.4.6nb2.
[*] Note that this behavior can be tweaked globally by setting
DLOPEN_REQUIRE_PTHREADS to "yes" or "no" in /etc/mk.conf.
Most important change was serious bug in 3.5 that did not allow DB-API 2.0
version to work without a manual change.
Other changes:
- Better DB-API 2.0 compliance
- Exception hierarchy moved into C module and made available to both APIs
- Fix error in update method that caused false exceptions
- Moved to standard exception hierarchy in classic API
- Added new method to get transaction state
- Use proper Python constants where appropriate
- Use Python versions of strtol, etc. Allows WIN32 build
- Bug fixes and cleanups
- Fix permissions on config file as it could contain sensitive data
- Fix missing ChangeLog link
- Lots of bugfixes and updates, see ChangeLog for all the details
- Inclues security update for PMASA-2004-4
Add HOMEPAGE pointing into search.cpan.org.
Add DEPENDS on p5-Cache-Simple-TimedExpiry, as that appears to be required
to have "make test" complete.
Change log:
1.15 Sat Nov 27 13:09:56 EST 2004
- Fix a testsuite bug when DBD::SQLite isn't there
1.14
- Silenced warnings about uninitialized warnings when inserting null cols
into the database.
- Started adding lowercase method name aliases
- Minor refactoring of 'id' method for a stupid, tiny perf improvement
- Refactoring of DBIx::SearchBuilder::Record::Cachable for performance
improvement
- Added a FlushCache method to DBIx::SearchBuilder::Record::Cachable.
- Started to flesh out a...test suite
- SearchBuilder now truncates strings before inserting them into character
types in the database as mysql generally does. Additionally, it truncates
things at utf8 character boundaries...as mysql does not.
- Fix for an undefined record cache warning on load from Autrijus Tang
- Major documentation cleanups --Simon Cavalletto
- A few tweaks to the ::Record class to eliminate the
hard-coding of the name of the id column --Simon Cavalletto
1.12
- Better error handling for some query build failure cases
- Corrected query builder for SQLite
- More refactoring.
1.11
- When loading an object whose "id" has been altered, as in
the case of RT's "Merge" functionality, the wrong object was
returned by the caching layer. Special casing for the "id"
method was removed.
1.10
- Identical to 1.10_05
1.10_05
- Reworked the _Accessible mechanism in DBIx::SearchBuilder::Record to
remove a horribly crufty old caching mechanism that created a copy
of the accessible hash for each and every object instantiated,
sometimes quite slowly.
1.10_04 Mon Aug 30 17:33:18 EDT 2004
A query builder fix for an issue that bit RT2:
Unsatisfied dependency chain in Joins Users_2 at /usr/local/share/perl/5.8.3/DBIx/SearchBuilder/Handle.pm line 965, line 69.
Stack:
[/usr/local/share/perl/5.8.3/DBIx/SearchBuilder/Handle.pm:965]
[/usr/local/share/perl/5.8.3/DBIx/SearchBuilder.pm:326]
[/usr/local/share/perl/5.8.3/DBIx/SearchBuilder.pm:119]
[/usr/local/share/perl/5.8.3/DBIx/SearchBuilder.pm:410]
1.10_03 Mon Aug 30 14:31:10 EDT 2004
- Cache Sanity fixes from Autrijus Tang <autrijus@autrijus.org>
1.10_02 Thu Aug 26 13:31:13 EDT 2004
1.10_01 Thu Aug 26 00:08:31 EDT 2004
- Reimplemented DBIx::SearchBuilder:::Record::Cachable
to use Cache::Simple::TimedExpiry. This should make it faster and more
memory efficient.
1.02_03 Thu Jul 22 13:29:17 EDT 2004
- Additional bullet proofing for joins.
Now we default to ALIAS1 being "main" (cubic@acronis.ru)
1.02_02 Tue Jul 20 13:06:06 EDT 2004
- Fixed a join bug that mostly manifests as a 'Dependency chain'
error on RT2.
1.02_01 Wed Jul 7 12:28:08 EDT 2004
- magic _Object instantiation from cubic@acronis.ru
- make SB::_Handle settable directly (cubic@acronis.ru)
- document the above
Change log:
Changes in DBI 1.46 (svn rev 584), 16th November 2004
Fixed parsing bugs in DBI::SQL::Nano thanks to Jeff Zucker.
Fixed a couple of bad links in docs thanks to Graham Barr.
Fixed test.pl Win32 undef warning thanks to H.Merijn Brand & David Repko.
Fixed minor issues in DBI::DBD::Metadata thanks to Steffen Goeldner.
Fixed DBI::PurePerl neat() to use double quotes for utf8.
Changed execute_array() definition, and default implementation,
to not consider scalar values for execute tuple count. See docs.
Changed DBD::File to enable ShowErrorStatement by default,
which affects DBD::File subclasses such as DBD::CSV and DBD::DBM.
Changed use DBI qw(:utils) tag to include $neat_maxlen.
Updated Roadmap and ToDo.
Added data_string_diff() data_string_desc() and data_diff()
utility functions to help diagnose Unicode issues.
All can be imported via the use DBI qw(:utils) tag.
Changes in DBI 1.45 (svn rev 480), 6th October 2004
Fixed DBI::DBD code for drivers broken in 1.44.
Fixed "Free to wrong pool"/"Attempt to free unreferenced scalar" in FETCH.
Changes in DBI 1.44 (svn rev 478), 5th October 2004
Fixed build issues on VMS thanks to Jakob Snoer.
Fixed DBD::File finish() method to return 1 thanks to Jan Dubois.
Fixed rare core dump during global destruction thanks to Mark Jason Dominus.
Fixed risk of utf8 flag persisting from one row to the next.
Changed bind_param_array() so it doesn't require all bind arrays
to have the same number of elements.
Changed bind_param_array() to error if placeholder number <= 0.
Changed execute_array() definition, and default implementation,
to effectively NULL-pad shorter bind arrays.
Changed execute_array() to return "0E0" for 0 as per the docs.
Changed execute_for_fetch() definition, and default implementation,
to return "0E0" for 0 like execute() and execute_array().
Changed Test::More prerequisite to Test::Simple (which is also the name
of the distribution both are packaged in) to work around ppm behaviour.
Corrected docs to say that get/set of unknown attribute generates
a warning and is no longer fatal. Thanks to Vadim.
Corrected fetchall_arrayref() docs example thanks to Drew Broadley.
Added $h1->swap_inner_handle($h2) sponsored by BizRate.com
Changes in DBI 1.43 (svn rev 377), 2nd July 2004
Fixed connect() and connect_cached() RaiseError/PrintError
which would sometimes show "(no error string)" as the error.
Fixed compiler warning thanks to Paul Marquess.
Fixed "trace level set to" trace message thanks to H.Merijn Brand.
Fixed DBD::DBM $dbh->{dbm_tables}->{...} to be keyed by the
table name not the file name thanks to Jeff Zucker.
Fixed last_insert_id(...) thanks to Rudy Lippan.
Fixed propagation of scalar/list context into proxied methods.
Fixed DBI::Profile::DESTROY to not alter $@.
Fixed DBI::ProfileDumper new() docs thanks to Michael Schwern.
Fixed _load_class to propagate $@ thanks to Drew Taylor.
Fixed compile warnings on Win32 thanks to Robert Baron.
Fixed problem building with recent versions of MakeMaker.
Fixed DBD::Sponge not to generate warning with threads.
Fixed DBI_AUTOPROXY to work more than once thanks to Steven Hirsch.
Changed TraceLevel 1 to not show recursive/nested calls.
Changed getting or setting an invalid attribute to no longer be
a fatal error but generate a warning instead.
Changed selectall_arrayref() to call finish() if
$attr->{MaxRows} is defined.
Changed all tests to use Test::More and enhanced the tests thanks
to Stevan Little and Andy Lester. See http://qa.perl.org/phalanx/
Changed Test::More minimum prerequisite version to 0.40 (2001).
Changed DBI::Profile header to include the date and time.
Added DBI->parse_dsn($dsn) method.
Added warning if build directory path contains whitespace.
Added docs for parse_trace_flags() and parse_trace_flag().
Removed "may change" warnings from the docs for table_info(),
primary_key_info(), and foreign_key_info() methods.
Changes in DBI 1.42 (svn rev 222), 12th March 2004
Fixed $sth->{NUM_OF_FIELDS} of non-executed statement handle
to be undef as per the docs (it was 0).
Fixed t/41prof_dump.t to work with perl5.9.1.
Fixed DBD_ATTRIB_DELETE macro thanks to Marco Paskamp.
Fixed DBI::PurePerl looks_like_number() and $DBI::rows.
Fixed ref($h)->can("foo") to not croak.
Changed attributes (NAME, TYPE etc) of non-executed statement
handle to be undef instead of triggering an error.
Changed ShowErrorStatement to apply to more $dbh methods.
Changed DBI_TRACE env var so just does this at load time:
DBI->trace(split '=', $ENV{DBI_TRACE}, 2);
Improved "invalid number of parameters" error message.
Added DBI::common as base class for DBI::db, DBD::st etc.
Moved methods common to all handles into DBI::common.
Major tracing enhancement:
Added $h->parse_trace_flags("foo|SQL|7") to map a group of
trace flags into the corresponding trace flag bits.
Added automatic calling of parse_trace_flags() if
setting the trace level to a non-numeric value:
$h->{TraceLevel}="foo|SQL|7"; $h->trace("foo|SQL|7");
DBI->connect("dbi:Driver(TraceLevel=SQL|foo):...", ...);
Currently no trace flags have been defined.
Added to, and reworked, the trace documentation.
Added dbivport.h for driver authors to use.
Major driver additions that Jeff Zucker and I have been working on:
Added DBI::SQL::Nano a 'smaller than micro' SQL parser
with an SQL::Statement compatible API. If SQL::Statement
is installed then DBI::SQL::Nano becomes an empty subclass
of SQL::Statement, unless the DBI_SQL_NANO env var is true.
Added DBD::File, modified to use DBI::SQL::Nano.
Added DBD::DBM, an SQL interface to DBM files using DBD::File.
Documentation changes:
Corrected typos in docs thanks to Steffen Goeldner.
Corrected execute_for_fetch example thanks to Dean Arnold.
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.
Change log:
0.26 10th October 2004
* Changed to allow Building with Berkeley DB 4.3
* added cds_lock and associated methods as a convenience to allow
safe updaing of database records when using Berkeley DB CDS mode.
* added t/cds.t and t/pod.t
* Modified the test suite to use "-ErrFile => *STDOUT" where
possible. This will make it easier to diagnose build issues.
* -Errfile will now accept a filehandle as well as a filename
This means that -ErrFile => *STDOUT will get all extended error
messages displayed directly on screen.
* Added support for set_shm_key & get_shm_key.
* Patch from Mark Jason Dominus to add a better error message
when an odd number of parameters are passed to ParseParameters.
* fixed off-by-one error in my_strdup
* Fixed a problem with push, pop, shift & unshift with Queue &
Recno when used in CDS mode. These methods were not using
a write cursor behind the scenes.
Problem reported by Pavel Hlavnicka.
Version 0.81 (tagged 22 Nov 2003, revision 279)
Bug Fixes:
* correct mistake in Usage Example, operator for wildcard searching
is ~, not =
* raise proper errors on various methods of Persistable when no
PersistenceManager is available, instead of NoMethodError
Version 0.80 (tagged 19 Nov 2003, revision 275)
Features:
* transaction logging, record information about time, committer and log
message as well as list of objects modified per transaction
* basic versioning support, retrieval of historic object states
* vaporadmin: removal of classes and all their instances using the "remove" command
* vaporadmin: modification of class' metadata using the "update" command
* new operator (~) for wildcard searches on Strings
Bug Fixes:
* allow SQL keywords as names of persistent attributes
* fix bug where camelCase variables would not be correctly set on object loading
* correctly transfer newly persistent objects back to transient state during
rollback(). This bug caused incomprehensible ObjectDeletedErrors when manually
or automatically rolling back.
* check REXML::Version instead of REXML::VERSION_MAJOR, which does not exist
in the REXML version that is included in Ruby 1.8
* minimize number of warnings issued when using `ruby -w', including those
from Ruby 1.8.x, that are issued regardless of -w
Incompatible Repository Changes: (Repository needs to be recreated from scratch)
* repository schema version 3
* add fields and tables for versioning
and this package covers both Ruby 1.8 base and 1.6 base.
This is a Ruby extension to DBM library (including Berkley DB's DBM
compatible one), which is actually a part of the Ruby distribution.
Changes since 3.4.1:
Features: added context-sensitive online help system, better support
for 8.0, "sticky" navigation, better grant/revole. syntax
highlightling for PL/*, better navigation.
Translations: added Romanian, Mongolian, Ukrainian, Hebrew, and updates
to others.
Bugs
* Fix that non-Auto mode import didn't work (Adrian Nida)
* Fix inability to drop constraints when using a non-english translation
* Work around MSIE's failure to handle downloads in SSL mode
* Allow insert, update, delete, references and trigger to be granted
and revoked on views.
See HISTORY for full new feature list.
* Use PTHREAD_AUTO_VARS=no to disable linking to libpthread all programs
and libraries, which is wrong.
* Set USE_LIBTOOL and GNU_CONFIGURE before including bsd.prefs.mk, so
the test for _OPSYS_MAX_CMDLEN is not skipped.
Bump PKGREVISION to each package respectively
(mysql-client and mysql4-client), closes PR pkg/28162 and PR pkg/28222.
libldap_r and slurpd. Patch those Makefiles (patch-aj, patch-ak) to
pass $(PTHREAD_CFLAGS) and $(PTHREAD_LDFLAGS) to the build. The
configure process correctly adds any necessary libraries, so adding
$(PTHREAD_LIBS) isn't needed. Bump the PKGREVISION since the LDAP
libraries are no longer linked against libpthread.
This fixes PR pkg/28259.
inter-process mutexes. In this case, we only care to use the native
threads. Bump the PKGREVISION since this means that non-native pthreads
platforms will no longer depend on GNU pth.
Changes from version 2.2.13 include numerous fixes for locking in the
Berkeley DB backend, SASL-encoding fixes in libldap, and many bug
fixes in slapd.
packages that depend on mysql-client, using buildlink3, and using
GNU PTH, the pthread library never gets pulled in by buildlink. This
caused the p5-DBD-mysql build to fail, which in turn caused the mytop
build to fail. The fix is to include mk/pthread.buildlink3.mk in
mysql4-client/buildlink3.mk.
This addresses PR#28162.
* Add a db1.builtin.mk file that detects whether DB-1.85 functionality
exists in the base system, and remove the distinction between
"native" and the other Berkeley DB packages -- we now refer to
db[1234]. This paves the way for any future databases/db1 package.
* USE_DB185 shouldn't need to be set by any packages -- its correct
value is now automatically determined by bdb.buildlink3.mk depending
on whether we explicitly request db1 or not. By default, if you
include bdb.buildlink3.mk, you want DB-1.85 functionality and
USE_DB185 defaults to "yes", but if you explicitly remove db1 from
the list of acceptable DBs, then USE_DB185 defaults to "no".
* Set BDB_LIBS to the library options needed to link against the DB
library when bdb.buildlink3.mk is included.
* We only add the DB library to the linker command automatically if
we want DB-1.85 functionality; otherwise assume that the package
configure process can figure out how to probe for the correct
headers and libraries.
Edit package Makefiles to nuke redundant settings of USE_DB185.
It's only really needed on Darwin but building there on all platforms
allows us to keep the same PLIST for all of them: buildling the backend
results in two more include files to be installed.
Per discussion with recht@ our dedicated postgresql74-* MAINTAINER ;)
Functionality added or changed:
* The --with-openssl option for configure now accepts a path
prefix as an argument. --with-openssl-includes and
--with-openssl-libs are still supported, but are needed only
to override the default values. (Bug #5494)
* Added new --without-man option to configure to suppress
building/installing the manual pages. (Bug #5379)
* InnoDB: New mysqld option --innodb-table-locks and session
variable innodb_table_locks (on by default). In applications
using AUTOCOMMIT=1, InnoDB's internal table locks can cause
deadlocks. You can set innodb_table_locks=0 in `my.cnf' to
remove that problem. See section 16.17 Restrictions on InnoDB
Tables. (Bug #3299, Bug #5998)
* InnoDB: Added the startup option and settable global variable
innodb_max_purge_lag for delaying INSERT, UPDATE and DELETE
operations when the purge operations are lagging. The default
value of this parameter is zero, meaning that there will not be
any delays. See section 16.13 Implementation of Multi-Versioning.
* InnoDB: Change error code to HA_ERR_ROW_IS_REFERENCED if we
cannot DROP a parent table because it is referenced by a FOREIGN
KEY constraint.
And a lot of bugfixes: http://dev.mysql.com/doc/mysql/en/News-4.0.22.html
it is still on by default to preserve compatibility (use option "-bdb" to
disable).
While here, fix typo in CONFIGURE_ARGS that had caused the dnssrv backend
not to build; bump PKGREVISION.
* Make mysql4-client build on NetBSD 1.[56]*
* Don't install mysqld and friends in mysql4-client (eww!)
* Remove an unneeded patch.
* Remove duplicated files in mysql4-client's PLIST.
Also, use assembler functions when MACHINE_ARCH == i386.
This closes PR pkg/27154, pkg/27720, pkg/27744 and pkg/28035.
BTW, I tested them on NetBSD 1.6.2, 2.0_RC4 and -current.
Bump PKGREVISION for both packages.
Class::DBI provides a convenient abstraction layer to a database.
It not only provides a simple database to object mapping layer, but can
be used to implement several higher order database functions (triggers,
referential integrity, cascading delete etc.), at the application level,
rather than at the database.
This is particularly useful when using a database which doesn't support
these (such as MySQL), or when you would like your code to be portable
across multiple databases which might implement these things in
different ways.
In short, Class::DBI aims to make it simple to introduce 'best practice'
when dealing with data stored in a relational database.
only UI changes according to release announcements.
While here, introduce some package changes:
* handle config.inc.php via CONF_FILES mechanism instead of PLIST magick,
the symlink config.inc.php -> ${PKG_SYSCONFDIR}/config.inc.php is now
included in PLIST
* use NO_BUILD, NO_CONFIGURE
* Apache config fragment file is now installed as ${EXDIR}/apache.conf, not
copied to ${PKG_SYSCONFDIR} and MESSAGE points to the ${EXDIR} location
* do not install any *.sh files - they are developer stuff only
* use INSTALL_DATA for all files except scripts/convertcfg.pl
Ima::DBI attempts to organize and facilitate caching and more
efficient use of database connections and statement handles.
One of the things I always found annoying about writing large
programs with DBI was making sure that I didn't have duplicate
database handles open. I was also annoyed by the somewhat wasteful
nature of the prepare/execute/finish route I'd tend to go through
in my subroutines. The new DBI->connect_cached and DBI->prepare_cached
helped alot, but I still had to throw around global datasource,
username and password information.
So, after a while I grew a small library of DBI helper routines
and techniques. Ima::DBI is the culmination of all this, put into
a nice(?), clean(?) class to be inherited from.
It always struck me odd that DBI didn't take much advantage of Perl's
context sensitivity. DBIx::ContextualFetch redefines some of the various
fetch methods to fix this oversight. It also adds a few new methods for
convenience (though not necessarily efficiency).
so that we'd not force dependance on specific MySQL version, and instead pick
the currently installed mysql*-client (or install the default if there
is no mysql-client package installed yet)
this makes package buildable with arbitrary MySQL version, such as 3.23.x,
4.0.x or 4.1.x
MySQL version 4.1 offers dozens of important product enhancements
and new features, including support for:
* Subqueries and derived tables -- allowing users to search
complex data sets with greater ease and efficiency;
* A significantly faster and more flexible client-server protocol
with support for prepared statements, providing optimized query
execution and improved warning information;
* New GUI installer and configuration wizards for Linux and Windows,
making it easier for developers to set up and optimize their
MySQL databases;
* Encrypted client-server communication using OpenSSL (GPL),
greatly increasing security against malicious intrusion and
unauthorized access.
* A more highly-optimized MySQL server library with a smaller
memory footprint that performs significantly faster when embedded
in third-party software.
* Extensive Unicode support through the utf8 and ucs2 international
character sets for applications that require the use of local
languages;
* Industry-standard GIS spatial types for storing and managing
geographic data;
* Improved full text search and Help features.
* A vulnerability exists due to the insecure creation of temporary files,
which could possibly let a malicious user overwrite arbitrary files
* Repair possible failure to update hint bits on disk
Under rare circumstances this oversight could lead to "could not access
transaction status" failures, which qualifies it as a potential-data-loss bug.
* A vulnerability exists due to the insecure creation of temporary files,
which could possibly let a malicious user overwrite arbitrary files
* Repair possible failure to update hint bits on disk
Under rare circumstances this oversight could lead to "could not access
transaction status" failures, which qualifies it as a potential-data-loss bug.
release) and take maintainership.
Functionality added or changed:
# Print version_comment (from ./configure --comment during compilation)
when starting the server. E.g.: Version: '4.0.21-debug' socket:
'/tmp/mysql.sock' port: 0 Official MySQL Binary
# Made the MySQL server not react to signals SIGHUP and SIGQUIT on
Mac OS X 10.3. This is needed because under this OS, the MySQL server
receives lots of these signals (reported as Bug #2030).
# On Windows, the mysqld-nt and mysqld-max-nt servers now write error
messages to the Windows event log in addition to the MySQL error log.
Tons of bugfixes were fixed, more information:
http://dev.mysql.com/doc/mysql/en/News-4.0.21.html
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....
