发布于 2015-10-16 03:18:13 | 183 次阅读 | 评论: 0 | 来源: 网友投递

这里有新鲜出炉的Mysql教程,程序狗速度看过来!

Mysql关系型数据库管理系统

MySQL是一个开放源码的小型关联式数据库管理系统,开发者为瑞典MySQL AB公司。MySQL被广泛地应用在Internet上的中小型网站中。由于其体积小、速度快、总体拥有成本低,尤其是开放源码这一特点,许多中小型网站为了降低网站总体拥有成本而选择了MySQL作为网站数据库。


MySQL JDBC 驱动 5.1.37 版本发布,兼容 JDBC 4.2API,带来部分新功能,修复许多 bug,包括之前发现的连接 5.0 或者 5.1 服务器异常的回归问题。

MySQL Connector/J 5.1.37 是个维护版本,适用于 MySQL 5.5/5.6/5.7 版本。这是第一个支持 Java Database Connectivity 4.2 API 的版本。

新特性和改进

  • methodCompressedInputStream.getNextPacketFromServer()has been refactored to reduce memory use and garbage collection        efforts caused by the use of the inflater.       (Bug #21648826, Bug #78106)

  • The code for executing aREPLACEstatement        whenrewriteBatchedStatements=truehas been        refactored by putting multiple batched statements into a single        query, making it work more like anINSERTstatement. This increases the efficiency for runningREPLACEstatements. Thanks to Jie Han for        contributing the code.       (Bug #21429909, Bug #77681)

  • A new connection property,truncateFractionalSeconds=true|false, has        been introduced. It controls whether fractional seconds in        timestamps are to be truncated on the client side or to be sent        to the server side for truncation there. See the entry for the        new property in Driver/Datasource Class Names, URL Syntax and Configuration Properties for Connector/J for details. Thanks to Kwon Nam Son for contributing the code.       (Bug #21304726, Bug #77449)

  • Connector/J now supports the JSON data type, which has been        supported by the MySQL server since release 5.7.8.

  • A new connection property,enableEscapeProcessing, has been introduced        for supporting JDBC 4.2. It sets the default escape processing        behavior for Statement objects. See the entry for the new        property in Driver/Datasource Class Names, URL Syntax and Configuration Properties for Connector/J for details.

Bug 修复

  • AClassCastExceptionresulted for a Fabric        connection whenrewriteBatchedStatementswas “true” and a batch update was rewritten.       (Bug #21876798)

  • A number of regression tests in the testsuite failed when they        were run against MySQL 5.7, because theNO_AUTO_CREATE_USERSQL mode had become the        default behavior of the server since MySQL 5.7.7, making someGRANTstatements in the test fail when a new        user had to be created. With this fix,CREATE        USERstatements have been added to the regressions        tests when needed, to prevent the test failures.       (Bug #21697684, Bug #78225)

  • Connecting to MySQL 5.0 and 5.1 using Connector/J 5.1.36        resulted in anSQLException, with a complaint        for an “Unknown system variable 'language'”.       (Bug #21415165, Bug #77665)

  • TheIS_GENERATEDCOLUMNfield was empty in the        result returned byDatabaseMetaData.getColumns(). This fix        corrects the field so that it contains aYESorNOaccording to whether the column is        generated or not.       (Bug #20969312, Bug #76859)

  • getTypeInfo()returned an incorrectPRECISIONvalue of “255” for the        data type ofVARCHAR. The return value has        been corrected to “65535.” (Bug #20675539, Bug #76187)

  • When a connection is forcefully closed withabortInternal()in theConnectionImplclass, a null point exception        sometimes resulted. This is now avoided by putting the        associatedthis.io.releaseResources()call        inside a try block, so that the exception, unavoidable due to a        race condition, can be properly caught and ignored.       (Bug #20536592, Bug #75849)

  • If the MySQL server's default authentication method was SHA256        but neither one of the Connector/J connection propertiesallowPublicKeyRetrievalandserverRSAPublicKeyFilewas set, the        authentication failed with aTransientConnectionException, complaining        that the public key could not be retrieved. With this fix,        authentication continues in the situation, allowing other        enabled authentication methods to be tried.       (Bug #20433047, Bug #75670)

  • When a lock wait timeout occurred, anSQLExceptionwas thrown while anSQLTransientExceptionshould be thrown        instead. It was due to a wrong SQLState number used in the code,        which has now been fixed.       (Bug #16634180)

  • When the time zone on the MySQL server was configured to “GMT” but the client was in a different time zone,        Connector/J would make wrong adjustments for event timestamps        when working with the server.       (Bug #11758179, Bug #50348)

更多改进内容请看发行说明



历史版本 :
MySQL 8.0.4 RC 发布,带来大量新特性和改进
MySQL 5.7.21 发布,bug 修复和功能增加
MySQL 5.7.20 发布,bug 修复和功能增加
MySQL 8.0.3 RC 版即将发布,看看有哪些变化
MySQL 8.0.2 DMR 发布,添加 SQL window 函数
MySQL 5.7.19 发布,开源数据库服务器
MySQL 5.7.18 发布,数据库服务器
Galera 将死 — MySQL Group Replication 正式发布
MySQL 社区版 5.7.17 发布,数据库服务器
MySQL 5.7.16 发布,yaSSL 修复升级
MySQL 5.7.15 发布,新增 InnoDB 和 CMake 选项
MySQL 5.7.14 发布
最新网友评论  共有(0)条评论 发布评论 返回顶部

Copyright © 2007-2017 PHPERZ.COM All Rights Reserved   冀ICP备14009818号  版权声明  广告服务