Anzeigen der neuesten Beiträge
0 Mitglieder und 1 Gast betrachten dieses Thema.
3.5.2.0 (2012-07-07)- bug #3521416 [interface] JS error when editing index- bug #3521313 [core] Call to undefined function __()- bug #3521016 [edit] NOW() function incorrectly selected- bug [GUI] Invalid HTML code on transformation_overview.php- bug #3522930 [browse] Missing validation in Ajax mode- bug Fix popup message on build SQL of import- bug #3523499 [core] Make X-WebKit-CSP work better- replace Highcharts with jqplot for query profiling, zoom search- bug #3531584 [interface] No form validation in change password dialog- bug #3531585 [interface] Broken password validation in copy user form- bug #3531586 [unterface] Add user form prints JSON when user presses enter- bug #3534121 [config] duplicate line in config.sample.inc.php- bug #3534311 [interface] Grid editing incorrectly parses ENUM/SET values- bug #3510196 [core] More clever URL rewriting with ForceSSL
Ver 6.8 (2012/07/09) Stable Version- The main program updates ( Main ):Add: database object browser the new system tables ( SYSTEM TABLES ): (SQL Server / Sybase ASE / for Informix / Firebird / SQLite) (4573)Add: (MySQL) database object browser to the VIEWS increase SYSTEM VIEWS object (4573)Upd: (PostgreSQL) updated components Npgsql.dll 2.0.11.94 (2012/07/07) (4573)Upd: (DB2/Informix) updated components IBM.Data.DB2.dll / the IBM.Data.Informix.dll 9.7.4.4 (9.7.6.4) (2012/07/01) (4573)Fix: (SQL Server) Browse [all] database mode ( Browse all databases ) under AttachDb to fix heavy brush processing and database diagrams (4573)Add: Add disable indexing processing (Disable Indexes): (SQL Server / SQL Azure / Oracle) (4565)Add: Add rebuild the index treatment (Rebuild Indexes): (SQL Server / SQL Azure / Oracle / PostgreSQL / SQLite) (4565)Add: Add to reorganize the index processing Reorganize Indexes: (SQL Server) (4 565)Add: new index statistics update process (Update Statistics): the (SQLCe / Firebird / of Sybase ASE) (4565)Fix: (Sybase ASE) amendment object to specify a different Schema (4565)Fix: (Sybase ASE) fix the TRIGGERS object can not display the problem (4565)Upd: contains many small fixes and optimize the update ... the cumulative processing (4573)Misc: (DB2/Informix) the IBM Data Server Client the Packages Version 9.7 Fix Pack 6 (2012/07/03)Misc: Compatible with the MySQL 5.5.25a (2012/07/03)- SQL Editor ( SQL Editor ):Upd: optimization of auto-complete processing ( The AutoComplete * ):Upd: original only showed consistent [prefix] of the item (word), and another increase in [contains character items are displayed (Word%) (4573)Upd: listed in the project increased to 30, visual projects increased to 9 (4573)Fix: correction and open the main program (Database4.exe) and [different] when the database can not be their own proprietary syntax highlighting (4565)Add: Add the contents of the editor and grammar heavy brush shortcut key handling ( Refresh : Ctrl + R) (4 565)- Table ( Table Editor ):Upd: updated information on the type of case consistent treatment in the text display (including a script to generate DDL processing) (4565)Upd: (MySQL) to amend and update the ENUM SET data type, and DEFAULT is empty,'' display processing (including the script to generate DDL handle) (4565)Upd: (FoxPro) the DEFAULT quotes update string type, the original "" to'' the consistency of treatment (for other databases) (containing the script to generate DDL handle) (4565)Fix: (Sybase ASE) amend the DEFAULT settings can not be in the new mode to normal handling (including the script to generate DDL handle) (4565)
Ver 7.0 (2012/08/04) Stable Version- Table ( Table Editor ):Add: Add a constraint editor ( Constraint Editor ) (4599)Foreign Keys: Access / FoxPro / SQLite / Firebird / MySQL / PostgreSQL / Oracle / SQLCe / SQL Azure / SQL Server/DB2/Informix/SybaseASECheck Constraints: FoxPro / SQLite / Firebird / PostgreSQL / Oracle / SQL Azure / SQL Server/DB2/Informix/SybaseASEFix: Fixed (458?) Due to the type of field status updates, the impact of an existing table column the AutoIncrement the state (including the script DDL syntax generated) (4597)Fix: Fixed (4580) led to the table changes and close automatically refresh object message lost (4597), the original- Generated by the script ( Data Definition Language ):Upd: Update of CHECK constraints syntax to generate the ALTER TABLE handled automatically generated by the CREATE TABLE processing (4599)Upd: Update Foreign Keys syntax to generate: 1. Omitted Constraint Name display, processing automatically generated by the CREATE TABLE table name to join QuotedString (4599)Upd: (Access / Firebird) Foreign Keys syntax for excluding unwanted generation processing, the INDEXES object browser will also be omitted (display and processing and other databases) (4599)Fix: (Firebird) correction Multiple Foreign Keys field sort display problems (4599)Upd: (SQLite / Informix) update and support the Multiple Foreign the Keys syntax display processing (4597)Upd: substantial optimization of the generated update script (4599)- The main program updates ( Main ):Upd: (PostgreSQL / SybaseASE), update the table CONSTRAINTS object browsing, only display CHECK Type object with the other databases (4599)Upd: (PostgreSQL) update the table the INDEXES Object Browser Foreign the Keys do not make consistent with other databases (4599)Upd: (PostgreSQL) to update the table TRIGGERS object browser, the internal (Internal) default without display (4597)Upd: (FoxPro) to support a complete display of CHECK constraints object browser and DDL scripts display processing (formerly only supports 1) (4597)Add: New CREATE CONSTRAINT the establishment of the samples (4597)Upd: Update Database. NET Additional Files (2012/08/04)Upd: contains many small fixes and optimize the update ... the cumulative processing (4599)Misc: Compatible with SQL Server 2008 R2, SP2 / SQL Server 2008 R2, SP2 Express (2012/07/26)Misc: Compatible with the MySQL 5.5.27 (2012/07/23)- SQL Editor ( SQL Editor ):Upd: to enhance the field in a table automatically senses ( IntelliSense ) processing speed (4599)- Database Diagrams ( Database Diagram ):Fix: (MySQL / FoxPro) correction associated with deleted (Delete relationships) and the (MySQL) KEYS associated with the object browser to delete the role of problem (4597)Upd: (SQLite) remove the associated Delete (Delete relationships) option (due to the database itself does not support) (4597)
* Functionality Added or Changed- Important Change: The YEAR(2) data type is now deprecated because it is problematic. Support for YEAR(2) will be removed in a future release of MySQL.* Bugs Fixed- InnoDB: A race condition could cause assertion errors during a DROP TABLE statement for an InnoDB table. Some internal InnoDB functions did not correctly determine if a tablespace was missing; other functions did not handle the error code correctly if a tablespace was missing.- InnoDB: If a row was deleted from an InnoDB table, then another row was re-inserted with the same primary key value, an attempt by a concurrent transaction to lock the row could succeed when it should have waited. This issue occurred if the locking select used a WHERE clause that performed an index scan using a secondary index.- InnoDB: An assertion could be raised if an InnoDB table was moved to a different database using ALTER TABLE ... RENAME while the database was being dropped by DROP DATABASE.- InnoDB: Using the KILL statement to terminate a query could cause an unnecessary message in the error log: [ERROR] Got error -1 when reading table table_name- InnoDB: For an InnoDB table with a trigger, under the setting innodb_autoinc_lock_mode=1, sometimes auto-increment values could be interleaved when inserting into the table from two sessions concurrently. The sequence of auto-increment values could vary depending on timing, leading to data inconsistency in systems using replication.- Replication: An event whose length exceeded the size of the master dump thread's max_allowed_packet caused replication to fail. This could occur when updating many large rows and using row-based replication. As part of this fix, a new server option --slave-max-allowed-packet is added, which permits max_allowed_packet to be exceeded by the slave SQL and I/O threads. Now the size of a packet transmitted from the master to the slave is checked only against this value (available as the value of the slave_max_allowed_packet server system variable), and not against the value of max_allowed_packet.- Replication: Statements such as UPDATE ... WHERE primary_key_column = constant LIMIT 1 are flagged as unsafe for statement-based logging, despite the fact that such statements are actually safe. In cases where a great many such statements were run, this could lead to disk space becoming exhausted do to the number of such false warnings being logged. To prevent this from happening, a warning suppression mechanism is introduced. This warning suppression acts as follows: Whenever the 50 most recent ER_BINLOG_UNSAFE_STATEMENT warnings have been generated more than 50 times in any 50-second period, warning suppression is enabled. When activated, this causes such warnings not to be written to the error log; instead, for each 50 warnings of this type, a note is written to the error log stating The last warning was repeated N times in last S seconds. This continues as long as the 50 most recent such warnings were issued in 50 seconds or less; once the number of warnings has decreased below this threshold, the warnings are once again logged normally. The fix for this issue does not affect how these warnings are reported to MySQL clients; a warning is still sent to the client for each statement that generates the warning. This fix also does not make any changes in how the safety of any statement for statement-based logging is determined.- Replication: After upgrading a replication slave to MySQL 5.5.18 or later, enabling the query cache eventually caused the slave to fail.- The server did not build with gcc 4.7.- Certain arguments to RPAD() could lead to “uninitialized variable” warnings.- The presence of a file named .empty in the test database prevented that database from being dropped.- For some subqueries that should be executed using a range scan on a non-primary index and required use of filesort, only the first execution of the subquery was done as a range scan. All following executions were done as full table scans, resulting in poor performance.- The number of connection errors from a given host as counted by the server was periodically reset, with the result that max_connect_errors was never reached and invalid hosts were never blocked from trying to connect.- File access by the ARCHIVE storage engine was not instrumented and thus not shown in Performance Schema tables.- mysqlbinlog exited with no error code if file write errors occurred.- Using CONCAT() to construct a pattern for a LIKE pattern match could result in memory corrupting and match failure.- yaSSL rejected valid SSL certificates that OpenSSL accepts.- Sessions could end up deadlocked when executing a combination of SELECT, DROP TABLE, KILL, and SHOW ENGINE INNODB STATUS.- mysqldump could dump views and the tables on which they depend in such an order that errors occurred when the dump file was reloaded.
Autor
Thema: Datenbanksoftware und Tools diverses ... (Gelesen 90588 mal)
