New and enhanced features in Oracle NoSQL Database 2.0 include:
- Better Performance: enterprise-class elasticity with near linear scalability and under five millisecond latency enables users to dynamically grow a cluster as their data grows with no interruption in service. In recent performance tests, Oracle NoSQL Database 2.0 delivered more than a million YCSB operations per second on a 2.4 terabyte database on an 18-node commodity cluster setup. (1)
- Automatic Rebalancing: dynamic management of compute and storage resources to maintain SLAs in response to increased demand and changing processing requirements;
- Enhanced Manageability: a simple, easy to use web console to manage all aspects of deployment and monitoring, as well as document management and structured data management in one product;
- New APIs: a new C API helps improve developer productivity, a new Large Object API supports efficient Large Object management, and new automatic serialization APIs simplify application development;
- Tighter Integration with Oracle Database: Oracle Database users can view and query Oracle NoSQL Database records directly from SQL via External Tables, making NoSQL data immediately accessible and available for integrated analysis;
- Improved Management & Monitoring Support: SNMP/JMX support enables integration with Oracle and third party management tools;
- Improved Hadoop Integration: tighter integration with Hadoop through JSON object and schema evolution support for data storage and serialization using Avro.
Download a partire da questa pagina.
MySQL 5.5.21 is a new version of the 5.5 production release of the world's most popular open source database. MySQL 5.5.21 is recommended for use on production systems. MySQL 5.5 includes several high-impact enhancements to improve the performance and scalability of the MySQL Database, taking advantage of the latest multi-CPU and multi-core hardware and operating systems. In addition, with release 5.5, InnoDB is now the default storage engine for the MySQL Database, delivering ACID transactions, referential integrity and crash recovery by default.
Functionality Added or Changed
Performance: InnoDB Storage Engine: Memory allocation for InnoDB tables was reorganized to reduce the memory overhead for large numbers of tables or partitions, avoiding situations where the "resident set size" could grow regardless of FLUSH TABLES statements. The problem was most evident for tables with large row size. Some of the memory that was formerly allocated for every open table is now allocated only when the table is modified for the first time. (Bug #11764622, Bug #57480)
Incompatible Change: An earlier change (in MySQL 5.1.62 and 5.5.21) was found to modify date-handling behavior in General Availability-status series (MySQL 5.1 and 5.5). This change has been reverted.
The change was that several functions became more strict when passed a DATE() function value as their argument, thus they rejected incomplete dates with a day part of zero. These functions were affected: CONVERT_TZ(), DATE_ADD(), DATE_SUB(), DAYOFYEAR(), LAST_DAY(), TIMESTAMPDIFF(), TO_DAYS(), TO_SECONDS(), WEEK(), WEEKDAY(), WEEKOFYEAR(), YEARWEEK(). The previous behavior has been restored. (Bug #13458237)
InnoDB Storage Engine: A Valgrind error was fixed in the function os_aio_init(). (Bug #13612811)
InnoDB Storage Engine: The server could crash when creating an InnoDB temporary table under Linux, if the $TMPDIR setting points to a tmpfs filesystem and innodb_use_native_aio is enabled, as it is by default in MySQL 5.5.4 and higher. The entry in the error log looked like:
101123 2:10:59 InnoDB: Operating system error number 22 in a file operation.
InnoDB: Error number 22 means 'Invalid argument'.
The crash occurred because asynchronous I/O is not supported on tmpfs in some Linux kernel versions. The workaround was to turn off the innodb_use_native_aio setting or use a different temporary directory. The fix causes InnoDB to turn off the innodb_use_native_aio setting automatically if it detects that the temporary file directory does not support asynchronous I/O. (Bug #13593888, Bug #11765450, Bug #58421)
InnoDB Storage Engine: References to C preprocessor symbols and macros HAVE_purify, UNIV_INIT_MEM_TO_ZERO, and UNIV_SET_MEM_TO_ZERO were removed from the InnoDB source code. They were only used in debug builds instrumented for Valgrind. They are replaced by calls to the UNIV_MEM_INVALID() macro. (Bug #13418934)
InnoDB Storage Engine: The MySQL server could halt with an assertion error:
InnoDB: Failing assertion: page_get_n_recs(page) > 1
Subsequent restarts could fail with the same error. The error occurred during a purge operation involving the InnoDB change buffer. The workaround was to set the configuration option innodb_change_buffering=inserts. (Bug #13413535, Bug #61104)
InnoDB Storage Engine: With 1024 concurrent InnoDB transactions running concurrently and the innodb_file_per_table setting enabled, a CREATE TABLE operation for an InnoDB table could fail. The .ibd file from the failed CREATE TABLE was left behind, preventing the table from being created later, after the load had dropped.
The fix adds error handling to delete the erroneous .ibd file. This error was less likely to occur in MySQL 5.5 and 5.6, because raising the number of InnoDB undo slots increased the number of simultaneous transactions needed to trigger the bug, from 1K to 128K. (Bug #12400341)
Replication: Executing mysqlbinlog with the --start-position=N option, where N was equal either to 0 or to a value greater than the length of the dump file, caused it to crash.
This issue was introduced in MySQL 5.5.18 by the fix for Bug #32228 and Bug #11747416. (Bug #13593869, Bug #64035)
Replication: On Windows replication slave hosts, STOP SLAVE took an excessive length of time to complete when the master was down. (Bug #11752315, Bug #43460)
A query that used an index on a CHAR column referenced in a BETWEEN clause could return invalid results. (Bug #13463488, Bug #63437)
Expressions that compared a BIGINT column with any non-integer constant were performed using integers rather than decimal or float values, with the result that the constant could be truncated. This could lead to any such comparison that used <, >, <=, >=, =, !=/<>, IN, or BETWEEN yielding false positive or negative results. (Bug #13463415, Bug #11758543, Bug #63502, Bug #50756)
When the optimizer performed conversion of DECIMAL values while evaluating range conditions, it could produce incorrect results. (Bug #13453382)
When running mysqldump with both the --single-transaction and --flush-logs options, the flushing of the log performed an implicit COMMIT (see Section 12.3.3, "Statements That Cause an Implicit Commit"), causing more than one transaction to be used and thus breaking consistency. (Bug #12809202, Bug #61854)
It was possible in the event of successive failures for mysqld_safe to restart quickly enough to consume excessive amounts of CPU. Now, on systems that support the sleep and date system utilities, mysqld_safe checks to see whether it has restarted more than 5 times in the current second, and if so, waits 1 second before attempting another restart. (Bug #11761530, Bug #54035)
When used with the --xml option, mysqldump --routines failed to dump any stored routines, triggers, or events. (Bug #11760384, Bug #52792)
It was possible on replication slaves where FEDERATED tables were in use to get timeouts on long-running operations, such as Error 1160 Got an error writing communication packets. The FEDERATED tables did not need to be replicated for the issue to occur. (Bug #11758931, Bug #51196)
References: See also Bug #12896628, Bug #61790.
If an attempt to initiate a statement failed, the issue could not be reported to the client because it was not prepared to receive any error messages prior to the execution of any statement. Since the user could not execute any queries, they were simply disconnected without providing a clear error.
After the fix for this issue, the client is prepared for an error as soon as it attempts to initiate a statement, so that the error can be reported prior to disconnecting the user. (Bug #11755281, Bug #47032)
Using myisamchk with the sort recover method to repair a table having fixed-width row format could cause the row pointer size to be reduced, effectively resulting in a smaller maximum data file size. (Bug #48848, Bug #11756869)
On Windows, the server incorrectly constructed the full path name of the plugin binary for INSTALL PLUGIN and CREATE FUNCTION ... SONAME. (Bug #45549, Bug #11754014)
The stored routine cache was subject to a small memory leak that over time or with many routines being used could result in out-of-memory errors. (Bug #44585, Bug #11753187)
- [interface] TextareaAutoSelect feature broken
- [export] PHP Array export might generate invalid php code
- [import] Import from ODS ignores cell that is the same as cell before
- [display] SELECT DISTINCT displays wrong total records found
- [operations] copy table data missing SET SQL_MODE=´NO_AUTO_VALUE_ON_ZERO´
-  Setting data to NULL and drop-downs
-  Missing set fields and values in generated INSERT query
- [libraries] license issue with TCPDF (updated to 5.9.145)
Download da questa pagina.
Rilasciata la versione 7.0.1 di NetBeans, la nuova versione è certificata per la versione finale di Java 7 rilasciata qualche giorno fa. NetBeans 7.0 era stato rilasciato ad aprile. Le note di rilascio sono disponibili a questa pagina, il download è possibile da questa pagina.
NetBeans IDE 7.0.1 is an update to NetBeans IDE 7.0 and includes the following changes:
- Full certification on the final release of JDK 7
- Bundle GlassFish 3.1.1 update release
- WebLogic related enhancements
- Significant quality increase
The following updates to the 7.0 release also apply to 7.0.1:
- Oracle Database improvements
- HTML5 editing support
- Maven 3 is supported and bundled with the IDE
- Improved support for CDI, REST services, Java Persistence, and Bean Validation
- PHP Rename Refactoring
- Line wrapping
- Improved detection of external changes (native file system listening)
- Updates to the C/C++ support (remote file system browsing, library projects running/debugging, enhanced templates/specializations)
- Support for Git 1.7.х
- Additional enhancements are listed at the NetBeans IDE 7.0 page
The PostgreSQL Global Development Group today released updates for all active branches of the PostgreSQL object-relational database system, including versions 9.0.2, 8.4.6, 8.3.13, 8.2.19, 8.1.23. Database administrators are strongly encouraged to update at the next available downtime, particularly if using version 9.0, Point-In-Time Recovery or Warm Standby.
This release is the last update to PostgreSQL 8.1. Version 8.1 is now end-of-life, and users are encouraged to upgrade to a newer version as soon as possible. See our release support policy.
This release includes numerous documentation updates and 174 bugfixes.
Oracle ha annunciato il rilascio della versione 5.5 (5.5.8) di MySQL. Il MySQL Community Edition 5.5, che è rilasciato sotto licenza GPL (GNU General Public License), ed è disponibile per il download gratuito da questa pagina, comprende InnoDB come storage engine di default. In questa versione infatti MyISAM viene sostituito da InnoDB (sviluppato da Innobase, società controllata da Oracle) come storage engine predefinito.
MySQL 5.5 offre miglioramenti significativi permettendo agli utenti di migliorare le prestazioni e la scalabilità delle applicazioni web in più ambienti operativi, inclusi Windows, Linux, Oracle Solaris e Mac OS X.
Con il rilascio di MySQL 5.5 gli utenti trarranno beneficio da:
- Miglioramento delle prestazioni e scalabilità: MySQL database e lo storage engine InnoDB sono stati migliorati per offrire prestazioni ottimali e scalabilità quando sono in esecuzione sul più recente hardware e software disponibile (CPU multi-core e ultimi sistemi operativi disponibili). Inoltre, con questa versione InnoDB è ora lo storage engine predefinito per il database MySQL, offrendo transazioni ACID, l'integrità referenziale e crash recovery.
- Maggiore disponibilità: New semi-synchronous replication e Replication Heart Beat migliorano la velocità e l'affidabilità del failover.
- Migliorata l'usabilità: migliorati gli indici ed il partizionamento delle tabelle, supporto a SIGNAL / RESIGNAL, e la diagnostica avanzata, incluso un nuovo PERFORMANCE_SCHEMA, migliorata la gestibilità di MySQL 5.5.
La comunità KDE ha annunciato che il progetto KOffice cambierà nome e di chiamerà d'ora in poi "Suite Calligra", e il sito ufficiale diventerà www.calligra-suite.org. Secondo l'annuncio, "Il nuovo nome riflette il valore più ampio della piattaforma tecnologica". la "Suite Calligra" è costituita da un word processor (Word, noto in precedenza come KWord), da un foglio elettronico (Tables, noto in precedenza come KSpread), da un programma per presentazioni (Stage, noto in precedenza come KPresenter), un programma per disegnare diagrammi (Flow, noto in precedenza come Kivio), e da un database (Kexi, simile a Microsoft Access). Un software per il Project Management (Plan, noto in precedenza come Plato), e due applicazioni per il disegno: Krita, e Karbon editor di immagini vettoriali.
Rilasciata la versione 126.96.36.199 di phpMyAdmin, software freeware scritto in Php che consente di amministrare Database MySQL sul web (http://bit.ly/eBN0XH).
Si tratta di un aggiornamento di sicurezza che risolve un problema di attacco XSS (http://bit.ly/fF4hPh).
Download possibile da questa pagina: http://bit.ly/ggBvxM.