Zend Framework 0.1.3 - 2006-05-31 08:48:28



So, why yet-another-framework? Clearly, it's useful to have a standard library of components that you can drop into your applications.

There are plans for AJAX, SMTP, and web services components, among others. As you can probably deduce from the names, the components already implemented include the ActiveRecord pattern, some glue for MVC, flexible logging and templating and a security related input filtering class are also present. ZSearch provides document indexing capabilities, to make it easy to implement custom search engines for arbitrary documents stored in arbitrary storage containers.

One of the goals for the project is to keep every clear and simple to use, without forcing you to adopt the entire framework throughout your application; it doesn't impose itself on your app, and doesn't require any configuration files to deploy and use.

Ladda ner o prova:
http://framework.zend.com

Online manual:
http://framework.zend.com/manual

Poffens inlägg på PHPportalens forum:
http://www.phpportalen.net/viewtopic.php?t=64165

Citat:

Major benefits of Zend Framework :!: I see a wide array of benefits to using the Zend Framework: 1. Free license 2. Entire framework created from scratch - no obsolete code over-head hanging around for backward compatibility 3. Support and insistence of PHP 5 4. Extreme simplicity - easy to learn/use 5. Light weight - so it can be used on very large websites 6. Free from IP infringement issues - very important! 7. Use only what you need in your logic. This feature used to be called serviced-based architecture (SBA) - instantiate only what you want on a need-to-use basis. I worked on SBA on Power Builder/PFC before and can say it is the most optimal architecture. This keeps the performance at its peak (can be used even on large websites) as we don't need to load/instantiate unnecessary classes into memory. If in doubt, try defining a couple of classes inside a single file, include it in another PHP file and run the debugger - you would notice it pre-loads each and every class found in the file into memory although class definitions themselves are not executable unless invoked/instantiated. I only hope they don't restrict us from using templating engines such as Smarty, Savant... Shekar

Nyheten inskickad av poffen    

MySQL 4.0.27 - 2006-05-13 14:36:50

Hi,

MySQL 4.0.27, a new version of the popular Open Source Database
Management System, has been released. The Community Edition is now
available in source and binary form for a number of platforms from our
download pages at

http://dev.mysql.com/downloads/mysql/4.0.html
http://downloads.mysql.com/archives.php?p=mysql-4.0&v=4.0.27

and mirror sites.

This is a security fix release and bugfix release for the 4.0
production release family.

This MySQL 4.0.27 release includes the patches for recently reported
security vulnerabilities in the MySQL client-server protocol. We would
like to thank Stefano Di Paola for finding
and reporting these to us.

Functionality added or changed:

* The MySQL-server RPM now explicitly assigns the mysql system
user to the mysql user group during the post-installation
process. This corrects an issue with upgrading the server on
some Linux distributions whereby a previously existing mysql
user was not changed to the mysql group, resulting in wrong
groups for files created following the installation.
(Bug#12823: http://bugs.mysql.com/12823)

* Better detection of connection timeout for replication servers
on Windows allows elimination of extraneous Lost connection
errors in the error log.
(Bug#5588: http://bugs.mysql.com/5588)

Bugs fixed:

* Security fix: A malicious client, using specially crafted
invalid login or COM_TABLE_DUMP packets was able to read
uninitialized memory, which potentially, though unlikely in
MySQL, could have led to an information disclosure.
(CVE-2006-1516
(http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-1516),
CVE-2006-1517
(http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-1517))
Thanks to Stefano Di Paola stefano.dipaola@wisec.it for
finding and reporting this bug.

* MySQL-shared-compat-4.0.26-0.i386.rpm and 4.0.27 incorrectly
depend on glibc 2.3 and cannot not be installed on a glibc 2.2
system. For MySQL 4.0, we recommend using the older
MySQL-shared-compat-4.0.25-0.i386.rpm package.
(Bug#16539: http://bugs.mysql.com/16539)

* When myisamchk needed to rebuild a table, AUTO_INCREMENT
information was lost. (Bug#10405: http://bugs.mysql.com/10405)

* BIT_COUNT() could return an incorrect value for right table
columns in a LEFT JOIN.
(Bug#13044: http://bugs.mysql.com/13044)

* An UPDATE statement which tried to update a column with a name
beginning with an asterisk would cause the server to crash.
This was because the MySQL server would wrongly expand the '*'
character to the list of all table columns, causing the list of
columns to become longer than the list of values. Now the server
performs this expansion only if the '*' character is followed
by a space. (Bug#15610: http://bugs.mysql.com/15610)

* An INSERT ... SELECT statement between tables in a MERGE set
can return errors when statement involves insert into child
table from merge table or vice-versa.
(Bug#5390: http://bugs.mysql.com/5390)

* A LIMIT-related optimization failed to take into account that
MyISAM table indexes can be disabled, causing Error 124 when
it tried to use such an index.
(Bug#14616: http://bugs.mysql.com/14616)

* For a table that had been opened with HANDLER OPEN, issuing
OPTIMIZE TABLE, ALTER TABLE, or REPAIR TABLE caused a server
crash. (Bug#14397: http://bugs.mysql.com/14397)

* Queries of the form (SELECT ...) ORDER BY ... were being
treated as a UNION. This improperly resulted in only distinct
values being returned (because UNION by default eliminates
duplicate results). Also, references to column aliases in
ORDER BY clauses following parenthesized SELECT statements
were not resolved properly.
(Bug#7672: http://bugs.mysql.com/7672)

* SELECT DISTINCT with a GROUP BY clause caused a server crash.
(Bug#13855: http://bugs.mysql.com/13855)

* SHOW CREATE TABLE did not display any FOREIGN KEY clauses if a
temporary file could not be created. Now SHOW CREATE TABLE
displays an error message in an SQL comment if this occurs.
(Bug#13002: http://bugs.mysql.com/13002)

* MySQL programs in binary distributions for Solaris 8/9/10 x86
systems would not run on Pentium III machines.
(Bug#6772: http://bugs.mysql.com/6772)

* Queries against a MERGE table that has a composite index could
produce incorrect results.
(Bug#9112: http://bugs.mysql.com/9112)

* The counters for the Key_read_requests, Key_reads,
Key_write_requests, and Key_writes status variables were
changed from "unsigned long" to "unsigned long long" to
accommodate larger values before the variables
roll-over and restart from 0.
(Bug#12920: http://bugs.mysql.com/12920)

* A concurrency problem for CREATE ... SELECT could cause a
server crash. (Bug#12845: http://bugs.mysql.com/12845)

* On HP-UX 11.x (PA-RISC), the -L option caused "mysqlimport" to
crash. (Bug#12958: http://bugs.mysql.com/12958)

* The server crashed when one thread resized the query cache
while another thread was using it.
(Bug#12848: http://bugs.mysql.com/12848)

Bugs fixed (for problems building from source):

* Avoid trying to include when it doesn't work
in C++ code. (Bug#13621: http://bugs.mysql.com/13621)

* MySQL would not compile on Linux distributions that use the
"tinfo" library. (Bug#18912: http://bugs.mysql.com/18912)

* Fixed problems with static variables to allow building on
Fedora Core 3. (Bug#6554: http://bugs.mysql.com/6554)

kent

--
Kent Boortz, Senior Software Developer
MySQL AB, www.mysql.com
Office: +46 18 174400 ext. 4450 (VoIP)
Office: +46 19 182931
Mobile: +46 70 2791171

Nyheten inskickad av hagman    

PHP 5.1.4 - 2006-05-06 11:07:34

PHP 5.1.4 Release Announcement

A critical bug with file uploads as well as the fastcgi sapi has been discovered in PHP 5.1.3 and a new PHP release 5.1.4 has been made available to address these two issues. All PHP users are encouraged to upgrade to this release as soon as possible.

This release provides fixes for the following bugs:

* Fixed problems with file uploads and the $_POST array handling.
* Resolved multiple problems with the FastCGI sapi.
* Fixed possible crash in highlight_string().
* Fixed cloning of DOM Documents and Noded.
* Several fixes to PDO ODBC driver.

For a full list of changes in PHP 5.1.4, see http://www.php.net/ChangeLog-5.php#5.1.4

Nyheten inskickad av insyman    

Camino 1.0.1 - 2006-05-04 19:45:36

Camino 1.0.1 is a security and stability update for Camino 1.0 users; all users are recommended to upgrade.

Changes since Camino 1.0

Since the 1.0 release, we have made the following changes and improvements:

* Fixed several critical security issues, including those fixed in version 1.8.0.3 of the Mozilla Gecko rendering engine.
* Upgraded the bundled Java Embedding Plugin (http://javaplugin.sf.net) to version 0.9.5+d
* Improved ad-blocking, especially of German ads
* Enabled the opening of local SVG files
* Fixed an issue where Camino on Intel-based Macs was unable to read Keychain entries stored by Camino on PowerPC-based Macs.

About Camino 1.0

After over a year of hard work by devoted volunteers, the Camino Project is proud to give you Camino 1.0. This latest version fixes hundreds of bugs and implements many new features, providing all users with an improved browsing experience.

Camino 1.0 brings you a heavily-updated version of the only native Mac OS X browser using Mozilla’s Gecko rendering engine. Thousands of bugs were fixed in Gecko 1.8, providing users with improved web page compatibility.

The features listed below are just some of the many in Camino 1.0.

Note: Due to major changes in Camino, Mac OS X 10.1 is no longer supported. Users still running Mac OS X 10.1 should continue to use Camino 0.8.5.

We want to know what you think! Be sure to contact us and let us know what you think.

What's New in Camino 1.0

Camino 1.0 brings a heavily updated version of the only native Mac OS X browser using Mozilla.org's Gecko HTML rendering engine (version 1.8), the same rendering engine used by the popular Firefox 1.5 web browser.

Here's what's new in Camino 1.0:

* Universal Binary - Camino is now a universal binary, allowing it to run natively on both PowerPC- and Intel-based Macs.
* New Tab Bar Appearance - The new tab bar appearance allows for easier usability.
* Download Manager Pause/Resume - The download manager now supports pause and resume and has been highly optimized and revised for better performance.
* Annoyance Blocking - With built-in ad- and pop-up blocking, Camino now allows you to ignore the things you hate most.
* Certificate Support - The addition of certificate support yields better security.
* Java Embedding Plugin - JEP improves Java performance immensely.
* Form Fill from Address Book - Form fill from Address Book makes filling in those pesky web forms much easier.
* History Searching - Finding past web pages is even easier with history searching built-in to the History Manager.
* Support for More Web Standards - Thanks to the Gecko rendering engine, Camino now supports SVG, the tag, and JavaScript 1.6, as well as improved CSS 2 and CSS 3 support.

See the complete release notes for a list of all changes from 0.8.4 to 1.0.

Downloading and Installing

System Requirements
Camino now requires Mac OS X 10.2 (users of 10.1 can download Camino 0.8.5 English) or Multilingual. In addition a minimum of 30 MB of free hard drive space and 128 MB or RAM is required.

Downloading Camino
You can download Camino from the main project page or directly from this link.

Installing Camino
Installing Camino is as simple as copying the app to your Applications folder. Instructions can be found on the disk image.

Known issues

* The recently released Real Player 10.1.0 (400) causes Camino to crash when viewing any Real content. This issue has been reported to Real, however, there is no time frame on a fix. Users are recommended to disable the Real Player plugin or install Real Player 10.0.0.
* Microsoft’s Windows Media Player (WMP) plugin causes major rendering issues in Camino. Since Microsoft has discontinued WMP on Mac OS X, Camino no longer supports the use of the WMP plugin; instead, all users should download the free Flip4Mac (F4M) plugin, version 2.0.2 or higher, from flip4mac.com. Version 2.0.2 causes pages containing WMP content to become white when scrolled in Camino; there is currently no ETA for a fixed version of F4M..
* Although typing performance has improved in Camino 1.0, typing in form fields can be slow when Flash or animated images are present. Turning off animations can improve performance in some cases.
* Shockwave Director content displays at the wrong location in the browser window when hardware rendering is enabled. Switch the plugin to software rendering to solve this.
* Java applets on some web pages may crash on Mac OS X 10.4 in certain configurations. This can happen after a system update fails to fully upgrade all components of the system. If you experience crashes on pages that use Java applets, apply or reapply the latest “combo update” from Apple to ensure that your system is up to date.
* Due to a bug in Mac OS X 10.2.x and 10.3.x, Norwegian users of Camino will need to manually set their 'accept-language' string. To set the accept-language string, add the string user_pref("camino.accept_languages", "nb,nn,no,en"); to your user.js file, where the languages are listed in the order in which you’d prefer them if a server can send content in multiple languages. (In this example, you want Bokmål first, then Nynorsk, then generic Norwegian, then English if none of the other three languages are available.) You may now launch Camino.

Apple fixed this bug in Mac OS X 10.4, so no work-arounds are necessary.
* Camino erroneously claims that the default Japanese and Traditional Chinese fonts are “missing” when they are actually installed; this is due to a mismatch between Carbon and Cocoa font names. Changing these fonts using the Camino user interface will result in incorrect fonts being chosen and will cause some characters to fail to display. Users should either keep the default fonts or change the fonts manually, ensuring the Carbon font names are used.
* Some users have experienced an issue where downloading files will cause Camino to hang when Quicksilver is installed. Users can work around this issue by either disabling indexing of the Desktop in Quicksilver or by setting the default download location to somewhere other than the Desktop in Camino’s Downloads preferences.

Nyheten inskickad av hagman    

MySQL 4.1.19 - 2006-05-04 19:39:26

Hi,


MySQL 4.1.19, a new version of the popular Open Source Database
Management System, has been released. The Community Edition is now
available in source and binary form for a number of platforms from our
download pages at
http://dev.mysql.com/downloads/ and mirror sites.

Note that not all mirror sites may be up to date at this point in time -
if you can't find this version on some mirror, please try again later or
choose another download site.

This is a bugfix release for the recent production release family.

This MySQL 4.1.19 release includes the patches for recently reported
security vulnerabilites in the MySQL client-server protocol. We would
like to thank Stefano Di Paola for finding
and reporting these to us.

This section documents all changes and bug fixes that have been
applied since the last official MySQL release. If you would like
to receive more fine-grained and personalised update alerts about
fixes that are relevant to the version and features you use,
please consider subscribing to MySQL Network (a commercial MySQL
offering). For more details please see
http://www.mysql.com/network/advisors.html.

We welcome and appreciate your feedback!



Functionality added or changed:
* Security enhancement: Added the global max_prepared_stmt_count
system variable to limit the total number of prepared
statements in the server. This limits the potential for
denial-of-service attacks based on running the server out of
memory by preparing huge numbers of statements. The current
number of prepared statements is available through the
prepared_stmt_count system variable.
(Bug#16365: http://bugs.mysql.com/16365)
* InnoDB now caches a list of unflushed files instead of
scanning for unflushed files during a table flush operation.
This improves performance when --innodb-file-per-table is set
on a system with a large number of InnoDB tables.
(Bug#15653: http://bugs.mysql.com/15653)
* New charset command added to mysql command-line client. By
typing charset name or \C name (such as \C UTF8), the client
character set can be changed without reconnecting.
(Bug#16217: http://bugs.mysql.com/16217)
* Large file support was re-enabled for the MySQL server binary
for the AIX 5.2 platform.
(Bug#13571: http://bugs.mysql.com/13571)
* When using the GROUP_CONCAT() function where the
group_concat_max_len system variable was greater than 512, the
type of the result was BLOB only if the query included an
ORDER BY clause; otherwise the result was a VARCHAR.
The result type of the GROUP_CONCAT() function is now VARCHAR
only if the value of the group_concat_max_len system variable
is less than or equal to 512. Otherwise, this function returns
a BLOB. (Bug#14169: http://bugs.mysql.com/14169)

Bugs fixed:
* Security fix: A malicious client, using specially crafted
invalid login or COM_TABLE_DUMP packets was able to read
uninitialized memory, which potentially, though unlikely in
MySQL, could have led to an information disclosure. Thanks to
Stefano Di Paola for finding and
reporting this bug.
* NDB Cluster: A simultaneous DROP TABLE and table update
operation utilising a table scan could trigger a node failure.
(Bug#18597: http://bugs.mysql.com/18597)
* NDB Cluster: Backups could fail for large clusters with many
tables, where the number of tables approached MaxNoOfTables.
(Bug#17607: http://bugs.mysql.com/17607)
* The IN-to-EXISTS transformation was making a reference to a
parse tree fragment that was left out of the parse tree. This
caused problems with prepared statements.
(Bug#18492: http://bugs.mysql.com/18492)
* Attempting to set the default value of an ENUM or SET column
to NULL caused a server crash.
(Bug#19145: http://bugs.mysql.com/19145)
* Index corruption could occur in cases when
key_cache_block_size was not a multiple of myisam_block_size
(for example, with key_cache_block_size=1536 and
myisam_block_size=1024).
(Bug#19079: http://bugs.mysql.com/19079)
* UNCOMPRESS(NULL) could cause subsequent UNCOMPRESS() calls to
return NULL for legal non-NULL arguments.
(Bug#18643: http://bugs.mysql.com/18643)
* Conversion of a number to a CHAR UNICODE string returned an
invalid result. (Bug#18691: http://bugs.mysql.com/18691)
* A call to MIN() with a CASE expression as its argument could
return a non-minimum value.
(Bug#17896: http://bugs.mysql.com/17896)
* A LOCK TABLES statement that failed could cause MyISAM not to
update table statistics properly, causing a subsequent CHECK
TABLE to report table corruption.
(Bug#18544: http://bugs.mysql.com/18544)
* Avoid trying to include when it doesn't work in
C++ code. (Bug#13621: http://bugs.mysql.com/13621)
* Executing SELECT on a large table that had been compressed
within myisampack could cause a crash.
(Bug#17917: http://bugs.mysql.com/17917)
* NDB Cluster: In a 2-node cluster with a node failure,
restarting the node with a low value for StartPartialTimeout
could cause the cluster to come up partitioned ("split-brain"
issue). (Bug#16447: http://bugs.mysql.com/16447)
A similar issue could occur when the cluster was first started
with a sufficiently low value for this parameter.
(Bug#18612: http://bugs.mysql.com/18612)
* NDB Cluster: On systems with multiple network interfaces, data
nodes would get "stuck" in startup phase 2 if the interface
connecting them to the management server was working on node
startup while the interface interconnecting the data nodes
experienced a temporary outage.
(Bug#15695: http://bugs.mysql.com/15695)
* mysql_config returned incorrect libraries on x86_64 systems.
(Bug#13158: http://bugs.mysql.com/13158)
* mysql_reconnect() sent a SET NAMES statement to the server,
even for pre-4.1 servers that do not understand the statement.
(Bug#18830: http://bugs.mysql.com/18830)
* During conversion from one character set to ucs2, multi-byte
characters with no ucs2 equivalent were converted to multiple
characters, rather than to 0x003F QUESTION MARK.
(Bug#15375: http://bugs.mysql.com/15375)
* The mysql_close() C API function leaked handles for
share-memory connections on Windows.
(Bug#15846: http://bugs.mysql.com/15846)
* The euro sign (€) was not stored correctly in columns using
the latin1_german1_ci or latin1_general_ci collation.
(Bug#18321: http://bugs.mysql.com/18321)
* The server was always built as though
--with-extra-charsets=complex had been specified.
(Bug#12076: http://bugs.mysql.com/12076)
* SELECT ... WHERE column LIKE 'A%' when column had a key and
used the latin2_czech_cs collation.
(Bug#17374: http://bugs.mysql.com/17374)
* A query using WHERE (column_1, column_2) IN ((value_1,
value_2)[, (..., ...), ...]) would return incorrect results.
(Bug#16248: http://bugs.mysql.com/16248)
* The -lmtmalloc library was removed from the output of
mysql_config on Solaris, as it caused problems when building
DBD::mysql (and possibly other applications) on that platform
that tried to use dlopen() to access the client library.
(Bug#18322: http://bugs.mysql.com/18322)
* When running a query that contained a GROUP_CONCAT( SELECT
GROUP_CONCAT(...) ), the result was NULL except in the ROLLUP
part of the result, if there was one.
(Bug#15560: http://bugs.mysql.com/15560)
* CASTdouble AS SIGNED INT) for large double values outside the
signed integer range truncates the result to be within range,
but the result sometimes had the wrong sign.
(Bug#15098: http://bugs.mysql.com/15098)
* SET value definitions containing commas were not rejected. Now
a definition such as SET('a,b','c,d') results in an error.
(Bug#15316: http://bugs.mysql.com/15316)
* MyISAM: Keys for which the first part of the key was a CHAR or
VARCHAR column using the UTF-8 character set and longer than
254 bytes could become corrupted.
(Bug#17705: http://bugs.mysql.com/17705)
* NDB Cluster: A timeout in the handling of an ABORT condition
with more that 32 operations could yield a node failure.
(Bug#18414: http://bugs.mysql.com/18414)
* NDB Cluster: A node restart immediately following a CREATE
TABLE would fail. Important: This fix supports 2-node Clusters
only. (Bug#18385: http://bugs.mysql.com/18385)
* NDB Cluster: In event of a node failure during a rollback, a
"false" lock could be established on the backup for that node,
which lock could not be removed without restarting the node.
(Bug#18352: http://bugs.mysql.com/18352)
* NDB Cluster: The cluster created a crashed replica of a table
having an ordered index --- or when logging was not enabled,
of a table having a table or unique index --- leading to a
crash of the cluster following 8 successibe restarts.
(Bug#18298: http://bugs.mysql.com/18298)
* NDB Cluster: When replacing a failed master node, the
replacement node could cause the cluster to crash from a
buffer overflow if it had an excessively large amount of data
to write to the cluster log.
(Bug#18118: http://bugs.mysql.com/18118)
* NDB Cluster: Restarting nodes were allowed to start and join
the cluster too early.
(Bug#16772: http://bugs.mysql.com/16772)
* If InnoDB encountered a HA_ERR_LOCK_TABLE_FULL error and
rolled back a transaction, the transaction was still written
to the binary log. (Bug#18283: http://bugs.mysql.com/18283)
* Connecting to a server with a UCS2 default character set with
a client using a non-UCS2 character set crashed the server.
(Bug#18004: http://bugs.mysql.com/18004)
* Character set conversion of string constants for UNION of
constant and table column was not done when it was safe to do
so. (Bug#15949: http://bugs.mysql.com/15949)
* Use of TRUNCATE TABLE for a TEMPORARY table on a master server
was propagated to slaves properly, but slaves did not
decrement the Slave_open_temp_tables counter properly.
(Bug#17137: http://bugs.mysql.com/17137)
* SELECT COUNT(*) for a MyISAM table could return different
results depending on whether an index was used.
(Bug#14980: http://bugs.mysql.com/14980)
* Large file support did not work in AIX server binaries.
(Bug#10776: http://bugs.mysql.com/10776)
* Security Improvement: GRANTs to users with wildcards in their
host information could be erroneously applied to similar users
with the same username and similar wildcards. For example, a
privilege granted to foo@% are also applied to user foo@192.%.
(Bug#14385: http://bugs.mysql.com/14385)
* NDB Cluster: Inserting and deleting BLOB column values while a
backup was in process could cause the loss of an ndbd node.
(Bug#14028: http://bugs.mysql.com/14028)
* Setting the myisam_repair_threads system variable to a value
larger than 1 could cause corruption of large MyISAM tables.
(Bug#11527: http://bugs.mysql.com/11527)
* Security improvement: In grant table comparisons, improper use
of a latin1 collation caused some hostname matches to be true
that should have been false. Thanks to Deomid Ryabkov for
finding this bug and proposing a solution.
(Bug#15756: http://bugs.mysql.com/15756)
* NDB Cluster: ndb_delete_all would run out of memory on tables
containing BLOB columns.
(Bug#16693: http://bugs.mysql.com/16693)
* A statement containing GROUP BY and HAVING clauses could
return incorrect results when the HAVING clause contained
logic that returned FALSE for every row.
(Bug#14927: http://bugs.mysql.com/14927)
* mysqldump tried to dump data from a view. (In MySQL 4.1, this
applies when connecting to a server from MySQL 5.0 or higher.)
(Bug#16389: http://bugs.mysql.com/16389)
* NDB Cluster: An UPDATE with an inner join failed to match any
records if both tables in the join did not have a primary key.
(Bug#17257: http://bugs.mysql.com/17257)
* NDB Cluster: A DELETE with a join in the WHERE clause failed
to retrieve any records if both tables in the join did not
have a primary key. (Bug#17249: http://bugs.mysql.com/17249)
* NDB Cluster: In some cases, LOAD DATA INFILE did not load all
data into NDB tables. (Bug#17081: http://bugs.mysql.com/17081)
* NDB Cluster: The REDO log would become corrupted (and thus
unreadable) in some circumstances, due to a failure in the
query handler. (Bug#17295: http://bugs.mysql.com/17295)
* NDB Cluster: No error message was generated for setting
NoOfFragmentLogFiles too low.
(Bug#13966: http://bugs.mysql.com/13966)
* NDB Cluster: No error message was generated for setting
MaxNoOfAttributes too low.
(Bug#13965: http://bugs.mysql.com/13965)
* Binary distributions for Solaris contained files with group
ownership set to the non-existing wheel group. Now the bin
group is used. (Bug#15562: http://bugs.mysql.com/15562)
* Killing a long-running query containing a subquery could cause
a server crash. (Bug#14851: http://bugs.mysql.com/14851)
* Repeated invocation of my_init() and my_end() caused
corruption of character set data and connection failure.
(Bug#6536: http://bugs.mysql.com/6536)
* A FULLTEXT query in a prepared statement could result in
unexpected behavior. (Bug#14496: http://bugs.mysql.com/14496)
* A FULLTEXT query in a UNION could result in unexpected
behavior. (Bug#16893: http://bugs.mysql.com/16893)
* Server crash when dropping InnoDB constraints named
TABLENAME_ibfk_0. (Bug#16387: http://bugs.mysql.com/16387)
* Corrected race condition when dropping the adaptive hash index
for a B-tree page in InnoDB.
(Bug#16582: http://bugs.mysql.com/16582)
* LOAD DATA FROM MASTER produced invalid warnings and Packet out
of order errors when the database already existed on the
slave. (Bug#15302: http://bugs.mysql.com/15302)
* A key on a MEMORY table would sometimes fail to match a row.
(Bug#12796: http://bugs.mysql.com/12796)
* MYSQL_STMT objects were not preserved following a connection
reset. Attempting to operate on them afterwards caused the
server to crash. (Bug#12744: http://bugs.mysql.com/12744)


Joerg

--
Joerg Bruehe, Senior Production Engineer
MySQL AB, www.mysql.com
Office: (+49 30) 417 01 487 VoIP: 4464@sip.mysql.com

Nyheten inskickad av hagman