with features that motivated me to update in ages and the two hours
I wasted trying to do an upgrade that required unreleased and pretty
much unbuildable perl modules over the weekend finished demotivating me.
Feature safe: yes
k3bscsicommand_bsd.cpp:96: error: 'struct scsi_sense_data' has no member named 'flags'
k3bscsicommand_bsd.cpp:97: error: 'struct scsi_sense_data' has no member named 'add_sense_code'
k3bscsicommand_bsd.cpp:98: error: 'struct scsi_sense_data' has no member named 'add_sense_code_qual'
[..]
Reported by: pointyhat
Feature safe: yes
src/abgx360.c: In function 'sendcdb':
src/abgx360.c:1815: error: 'struct scsi_sense_data' has no member named 'segment'
src/abgx360.c:1816: error: 'struct scsi_sense_data' has no member named 'flags'
src/abgx360.c:1817: error: 'struct scsi_sense_data' has no member named 'info'
[..]
Reported by: pointyhat
Feature safe: yes
active branches of the PostgreSQL object-relational database system,
including versions 9.1.2, 9.0.6, 8.4.10, 8.3.17 and 8.2.23.
This release contains 52 fixes to version 9.1, and a smaller number of
fixes to older versions, including:
- Fix bugs in information_schema.referential_constraints view**
- Correct collations for citext columns and indexes**
- Prevent possible crash when joining to a scalar function
- Prevent transitory data corruption of GIN indexes after a crash
- Prevent data corruption on TOAST columns when copying data
- Fix failures during hot standby startup
- Correct another "variable not found in subplan target list" bug
- Fix bug with sorting on aggregate expressions in windowing functions
- Multiple bug fixes for pg_upgrade
- Change Foreign Key creation order to better support
self-referential keys**
- Multiple bug fixes to CREATE EXTENSION
- Ensure that function return type and data returned from PL/perl agree
- Ensure that PL/perl strings are always UTF-8
- Assorted bug fixes for various Extensions
- Updates to the time zone database, particularly to CST6
Changes marked with ** above require additional, post-update steps in
order to fix all described issues.
URL: http://www.postgresql.org/docs/current/static/release.html
Also, fix a pthread problem in the FreeBSD port. [1]
PR: 160580 [1]
Feature safe: yes
The purpose of DBIx::Safe is to give controlled, limited access to an
application, rather than simply passing it a raw database handle through DBI.
DBIx::Safe acts as a wrapper to the database, by only allowing through the
commands you tell it to. It filters all things related to the database handle -
methods and attributes.
The typical usage is for your application to create a database handle via a
normal DBI call to new(), then pass that to DBIx::Safe->new(), which will return
you a DBIx::Safe object. After specifying exactly what is and what is not
allowed, you can pass the object to the untrusted application. The object will
act very similar to a DBI database handle, and in most cases can be used
interchangeably.
By default, nothing is allowed to run at all. There are many things you can
control. You can specify which SQL commands are allowed, by indicating the first
word in the SQL statement (e.g. 'SELECT'). You can specify which database
methods are allowed to run (e.g. 'ping'). You can specify a regular expression
that allows matching SQL statements to run (e.g. 'qr{SET TIMEZONE}'). You can
specify a regular expression that is NOT allowed to run (e.g. qr(UPDATE xxx}).
Finally, you can indicate which database attributes are allowed to be read and
changed (e.g. 'PrintError'). For all of the above, there are matching methods to
remove them as well.
WWW: http://search.cpan.org/dist/DBIx-Safe/
Feature safe: yes
String::ToIdentifier::EN provides a utility method, "to_identifier" for
converting an arbitrary string into a readable representation using the ASCII
subset of \w for use as an identifier in a computer program. The intent is to
make unique identifier names from which the content of the original string can
be easily inferred by a human just by reading the identifier.
If you need the full set of \w including Unicode, see the subclass
String::ToIdentifier::EN::Unicode.
Currently, this process is one way only, and will likely remain this way.
The default is to create camelCase identifiers, or you may pass in a separator
char of your choice such as _.
Binary char groups will be separated by _ even in camelCase identifiers to make
them easier to read, e.g.: foo_2_0xFF_Bar.
WWW: http://search.cpan.org/dist/String-ToIdentifier-EN/
Feature safe: yes
