56,679
社区成员
发帖
与我相关
我的任务
分享升星散分,提前祝大家新年快乐
以为要年后升星的,提前了一个星期,o(∩_∩)o ..发不了300分的帖子,用200分代替
在mysql版里学到很多,特别感谢:
ACMAIN_CHM,zuoxingyu,iihero,wwwwb等这些人的指点.新的一年,继续努力;
PS:
顺便带个mysql的问题:
打算玩下mysql5.5 不知道 和5.1的差距有多大,(网上说差距甚大)用过有体会的人发表下看法;
在mysql版里学到很多,特别感谢:
ACMAIN_CHM,zuoxingyu,iihero,wwwwb等这些人的指点.新的一年,继续努力;
PS:
顺便带个mysql的问题:
打算玩下mysql5.5 不知道 和5.1的差距有多大,(网上说差距甚大)用过有体会的人发表下看法;
...全文
请发表友善的回复…
发表回复
tt2com 2011-01-26
- 打赏
- 举报
mysqldbd 2011-01-26
- 打赏
- 举报
我明天就走了，提前预祝大家春节愉快，万事如意！
a4974 2011-01-26
- 打赏
- 举报
mysqldbd 2011-01-25
- 打赏
- 举报
[Quote=引用 23 楼 rucypli 的回复:]
我也要星星
[/Quote]
兄弟，你快了，很快就猩猩了！
我也要星星
[/Quote]
兄弟，你快了，很快就猩猩了！
rucypli 2011-01-25
- 打赏
- 举报
我也要星星
我是无聊至极的人 2011-01-25
- 打赏
- 举报
[Quote=引用 15 楼 xiaoyuanyuan2009 的回复:]5.5有精神病。 5.1有点乱码
[/Quote]
mysqldbd 2011-01-25
- 打赏
- 举报
[Quote=引用 20 楼 iihero 的回复:]
强烈的support...... :-)
5.5与5.1相比，有不少新特性。期待有人总结。
[/Quote]
只用稳定的，不怎么用5.5！
强烈的support...... :-)
5.5与5.1相比，有不少新特性。期待有人总结。
[/Quote]
只用稳定的，不怎么用5.5！
iihero_ 2011-01-25
- 打赏
- 举报
强烈的support...... :-)
5.5与5.1相比，有不少新特性。期待有人总结。
5.5与5.1相比，有不少新特性。期待有人总结。
shine333 2011-01-24
- 打赏
- 举报
nothingsss 2011-01-24
- 打赏
- 举报
祝贺下··
沉沦 2011-01-24
- 打赏
- 举报
祝贺下··
TzSword 2011-01-24
- 打赏
- 举报
哈哈，加油吧。
ACMAIN_CHM 2011-01-24
- 打赏
- 举报
mysql5.5 不知道 和5.1的差距有多大,
http://dev.mysql.com/doc/refman/5.5/en/mysql-nutshell.html
1.5. What Is New in MySQL 5.5
[+/-]
1.5.1. Scalability Improvements
1.5.2. InnoDB I/O Subsystem Changes
1.5.3. Enhanced Solaris Support
1.5.4. Diagnostic and Monitoring Capabilities
This section summarizes what has been added to and removed from MySQL 5.5.
Added Features
The following features have been added to MySQL 5.5:
•Improved scalability on multi-core CPUs. The trend in hardware development now is toward more cores rather than continued increases in CPU clock speeds, which renders “wait until CPUs get faster” a nonviable means of improving database performance. Instead, it is necessary to make better use of multiple cores to maximally exploit the processing cycles they make available. MySQL 5.5 takes advantage of features of SMP systems and tries to eliminate bottlenecks in MySQL architecture that hinder full use of multiple cores. The focus has been on InnoDB, especially locking and memory management. See Section 1.5.1, “Scalability Improvements”.
•InnoDB I/O subsystem changes enable more effective use of available I/O capacity. See Section 1.5.2, “InnoDB I/O Subsystem Changes”.
•Several modifications improve operation of MySQL Server on Solaris. See Section 1.5.3, “Enhanced Solaris Support”.
•There is better access to execution and performance information. Diagnostic improvements include DTrace probes, expanded SHOW ENGINE INNODB STATUS output, and a new status variable. See Section 1.5.4, “Diagnostic and Monitoring Capabilities”.
•The default storage engine for new tables is InnoDB rather than MyISAM. See Section 13.6.1, “InnoDB as the Default MySQL Storage Engine”.
•Support for an interface for semisynchronous replication: A commit performed on the master side blocks before returning to the session that performed the transaction until at least one slave acknowledges that it has received and logged the events for the transaction. Semisynchronous replication is implemented through an optional plugin component. See Section 17.3.8, “Semisynchronous Replication”
•Support for the SQL standard SIGNAL and RESIGNAL statements. See Section 12.7.8, “SIGNAL and RESIGNAL”.
•Support for Performance Schema, a feature for monitoring MySQL Server execution at a low level. See Chapter 21, MySQL Performance Schema.
•Support for additional Unicode character sets: utf16, utf32, and utf8mb4. These character sets support supplementary Unicode characters; that is, characters outside the Basic Multilingual Plane (BMP). See Section 9.1.10, “Unicode Support”.
•Enhancements to XML functionality, including a new LOAD XML statement.
•Two new types of user-defined partitioning are supported: RANGE COLUMNS partitioning is an extension to RANGE partitioning; LIST COLUMNS partitioning is an extension to LIST partitioning. Each of these extensions provides two enhancements to MySQL partitioning capabilities:
a.It is possible to define partitioning ranges or lists based on DATE, DATETIME, or string values (such as CHAR or VARCHAR).
You can also define ranges or lists based on multiple column values when partitioning tables by RANGE COLUMNS or LIST COLUMNS, respectively. Such a range or list may refer to up to 16 columns.
b.For tables defined using these partitioning types, partition pruning can now optimize queries with WHERE conditions that use multiple comparisons between (different) column values and constants, such as a = 10 AND b > 5 or a < "2005-11-25" AND b = 10 AND c = 50.
For more information, see Section 18.2.1, “RANGE Partitioning”, and Section 18.2.2, “LIST Partitioning”.
•It is now possible to delete all rows from one or more partitions of a partitioned table using the ALTER TABLE ... TRUNCATE PARTITION statement. Executing the statement deletes rows without affecting the structure of the table. The partitions named in the TRUNCATE PARTITION clause do not have to be contiguous.
•Key caches are now supported for indexes on partitioned MyISAM tables, using the CACHE INDEX and LOAD INDEX INTO CACHE statements. In addition, a key cache can be defined for and loaded with indexes from an entire partitioned table, or for one or more partitions. In the latter case, the partitions are not required to be contiguous.
•MySQL authentication supports two new capabilities, pluggable authentication and proxy users. With pluggable authentication, the server can use plugins to authenticate incoming client connections, and clients can load an authentication plugin that interacts properly with the corresponding server plugin. This capability enables clients to connect to the MySQL server with credentials that are appropriate for authentication methods other than the built-in MySQL authentication based on native MySQL passwords stored in the mysql.user table. For example, plugins can be created to use external authentication methods such as LDAP, Kerberos, PAM, or Windows login IDs. Proxy user capability enables a client who connects and authenticates as one user to be treated, for purposes of access control while connected, as having the privileges of a different user. In effect, one user impersonates another. Proxy capability depends on pluggable authentication because it is based on having an authentication plugin return to the server the user name that the connecting user impersonates. For information about these capabilities, see Section 5.5.6, “Pluggable Authentication”, and Section 5.5.7, “Proxy Users”.
•The TO_SECONDS() function is added. This function converts a date or datetime expression to a number of seconds since the year 0. You may use this function in partitioning expressions, and partition pruning is supported for tables defined using such expressions.
•MySQL releases are now built using CMake rather than the GNU autotools. Accordingly, the instructions for installing MySQL from source have been updated to discuss how to build MySQL using CMake. See Section 2.9, “Installing MySQL from Source”.
The build process is now similar enough on all platforms, including Windows, that there are no longer sections dedicated to notes for specific platforms.
Removed Features
The following constructs are obsolete and have been removed in MySQL 5.5. Where alternatives are shown, applications should be updated to use them.
•The log_bin_trust_routine_creators system variable (use log_bin_trust_function_creators).
•The myisam_max_extra_sort_file_size system variable.
•The record_buffer system variable (use read_buffer_size).
•The sql_log_update system variable.
•The table_type system variable (use storage_engine).
•The FRAC_SECOND modifier for the TIMESTAMPADD() function.
•The TYPE table option to specify the storage engine for CREATE TABLE or ALTER TABLE (use ENGINE).
•The SHOW TABLE TYPES SQL statement (use SHOW ENGINES).
•The SHOW INNODB STATUS and SHOW MUTEX STATUS SQL statements (use SHOW ENGINE INNODB STATUS SHOW ENGINE INNODB MUTEX).
•The SHOW PLUGIN SQL statement (use SHOW PLUGINS).
•The LOAD TABLE ... FROM MASTER and LOAD DATA FROM MASTER SQL statements (use mysqldump or mysqlhotcopy to dump tables and mysql to reload dump files).
•The BACKUP TABLE and RESTORE TABLE SQL statements (use mysqldump or mysqlhotcopy to dump tables and mysql to reload dump files).
•TIMESTAMP(N) data type: The ability to specify a display width of N (use without N).
•The --default-character-set and --default-collation server options (use --character-set-server and --collation-server).
•The --delay-key-write-for-all-tables server option (use --delay-key-write=ALL).
•The --enable-locking and --skip-locking server options (use --external-locking and --skip-external-locking).
•The --log-bin-trust-routine-creators server option (use --log-bin-trust-function-creators).
•The --log-long-format server option.
•The --log-update server option.
•The --master-xxx server options to set replication parameters (use the CHANGE MASTER TO statement instead): --master-host, --master-user, --master-password, --master-port, --master-connect-retry, --master-ssl, --master-ssl-ca, --master-ssl-capath, --master-ssl-cert, --master-ssl-cipher, --master-ssl-key.
•The --safe-show-database server option.
•The --skip-symlink and --use-symbolic-links server options (use --skip-symbolic-links and --symbolic-links).
•The --sql-bin-update-same server option.
•The --warnings server option (use --log-warnings).
•The --no-named-commands option for mysql (use --skip-named-commands
•The --no-pager option for mysql (use --skip-pager).
•The --no-tee option for mysql (use --skip-tee).
•The --position option for mysqlbinlog (use --start-position).
•The --all option for mysqldump (use --create-options).
•The --first-slave option for mysqldump (use --lock-all-tables).
•The --config-file option for mysqld_multi (use --defaults-extra-file).
•The --set-variable=var_name=value and -O var_name=value general-purpose options for setting program variables (use --var_name=value).
•The --with-pstack option for configure and the --enable-pstack option for mysqld.
http://dev.mysql.com/doc/refman/5.5/en/mysql-nutshell.html
1.5. What Is New in MySQL 5.5
[+/-]
1.5.1. Scalability Improvements
1.5.2. InnoDB I/O Subsystem Changes
1.5.3. Enhanced Solaris Support
1.5.4. Diagnostic and Monitoring Capabilities
This section summarizes what has been added to and removed from MySQL 5.5.
Added Features
The following features have been added to MySQL 5.5:
•Improved scalability on multi-core CPUs. The trend in hardware development now is toward more cores rather than continued increases in CPU clock speeds, which renders “wait until CPUs get faster” a nonviable means of improving database performance. Instead, it is necessary to make better use of multiple cores to maximally exploit the processing cycles they make available. MySQL 5.5 takes advantage of features of SMP systems and tries to eliminate bottlenecks in MySQL architecture that hinder full use of multiple cores. The focus has been on InnoDB, especially locking and memory management. See Section 1.5.1, “Scalability Improvements”.
•InnoDB I/O subsystem changes enable more effective use of available I/O capacity. See Section 1.5.2, “InnoDB I/O Subsystem Changes”.
•Several modifications improve operation of MySQL Server on Solaris. See Section 1.5.3, “Enhanced Solaris Support”.
•There is better access to execution and performance information. Diagnostic improvements include DTrace probes, expanded SHOW ENGINE INNODB STATUS output, and a new status variable. See Section 1.5.4, “Diagnostic and Monitoring Capabilities”.
•The default storage engine for new tables is InnoDB rather than MyISAM. See Section 13.6.1, “InnoDB as the Default MySQL Storage Engine”.
•Support for an interface for semisynchronous replication: A commit performed on the master side blocks before returning to the session that performed the transaction until at least one slave acknowledges that it has received and logged the events for the transaction. Semisynchronous replication is implemented through an optional plugin component. See Section 17.3.8, “Semisynchronous Replication”
•Support for the SQL standard SIGNAL and RESIGNAL statements. See Section 12.7.8, “SIGNAL and RESIGNAL”.
•Support for Performance Schema, a feature for monitoring MySQL Server execution at a low level. See Chapter 21, MySQL Performance Schema.
•Support for additional Unicode character sets: utf16, utf32, and utf8mb4. These character sets support supplementary Unicode characters; that is, characters outside the Basic Multilingual Plane (BMP). See Section 9.1.10, “Unicode Support”.
•Enhancements to XML functionality, including a new LOAD XML statement.
•Two new types of user-defined partitioning are supported: RANGE COLUMNS partitioning is an extension to RANGE partitioning; LIST COLUMNS partitioning is an extension to LIST partitioning. Each of these extensions provides two enhancements to MySQL partitioning capabilities:
a.It is possible to define partitioning ranges or lists based on DATE, DATETIME, or string values (such as CHAR or VARCHAR).
You can also define ranges or lists based on multiple column values when partitioning tables by RANGE COLUMNS or LIST COLUMNS, respectively. Such a range or list may refer to up to 16 columns.
b.For tables defined using these partitioning types, partition pruning can now optimize queries with WHERE conditions that use multiple comparisons between (different) column values and constants, such as a = 10 AND b > 5 or a < "2005-11-25" AND b = 10 AND c = 50.
For more information, see Section 18.2.1, “RANGE Partitioning”, and Section 18.2.2, “LIST Partitioning”.
•It is now possible to delete all rows from one or more partitions of a partitioned table using the ALTER TABLE ... TRUNCATE PARTITION statement. Executing the statement deletes rows without affecting the structure of the table. The partitions named in the TRUNCATE PARTITION clause do not have to be contiguous.
•Key caches are now supported for indexes on partitioned MyISAM tables, using the CACHE INDEX and LOAD INDEX INTO CACHE statements. In addition, a key cache can be defined for and loaded with indexes from an entire partitioned table, or for one or more partitions. In the latter case, the partitions are not required to be contiguous.
•MySQL authentication supports two new capabilities, pluggable authentication and proxy users. With pluggable authentication, the server can use plugins to authenticate incoming client connections, and clients can load an authentication plugin that interacts properly with the corresponding server plugin. This capability enables clients to connect to the MySQL server with credentials that are appropriate for authentication methods other than the built-in MySQL authentication based on native MySQL passwords stored in the mysql.user table. For example, plugins can be created to use external authentication methods such as LDAP, Kerberos, PAM, or Windows login IDs. Proxy user capability enables a client who connects and authenticates as one user to be treated, for purposes of access control while connected, as having the privileges of a different user. In effect, one user impersonates another. Proxy capability depends on pluggable authentication because it is based on having an authentication plugin return to the server the user name that the connecting user impersonates. For information about these capabilities, see Section 5.5.6, “Pluggable Authentication”, and Section 5.5.7, “Proxy Users”.
•The TO_SECONDS() function is added. This function converts a date or datetime expression to a number of seconds since the year 0. You may use this function in partitioning expressions, and partition pruning is supported for tables defined using such expressions.
•MySQL releases are now built using CMake rather than the GNU autotools. Accordingly, the instructions for installing MySQL from source have been updated to discuss how to build MySQL using CMake. See Section 2.9, “Installing MySQL from Source”.
The build process is now similar enough on all platforms, including Windows, that there are no longer sections dedicated to notes for specific platforms.
Removed Features
The following constructs are obsolete and have been removed in MySQL 5.5. Where alternatives are shown, applications should be updated to use them.
•The log_bin_trust_routine_creators system variable (use log_bin_trust_function_creators).
•The myisam_max_extra_sort_file_size system variable.
•The record_buffer system variable (use read_buffer_size).
•The sql_log_update system variable.
•The table_type system variable (use storage_engine).
•The FRAC_SECOND modifier for the TIMESTAMPADD() function.
•The TYPE table option to specify the storage engine for CREATE TABLE or ALTER TABLE (use ENGINE).
•The SHOW TABLE TYPES SQL statement (use SHOW ENGINES).
•The SHOW INNODB STATUS and SHOW MUTEX STATUS SQL statements (use SHOW ENGINE INNODB STATUS SHOW ENGINE INNODB MUTEX).
•The SHOW PLUGIN SQL statement (use SHOW PLUGINS).
•The LOAD TABLE ... FROM MASTER and LOAD DATA FROM MASTER SQL statements (use mysqldump or mysqlhotcopy to dump tables and mysql to reload dump files).
•The BACKUP TABLE and RESTORE TABLE SQL statements (use mysqldump or mysqlhotcopy to dump tables and mysql to reload dump files).
•TIMESTAMP(N) data type: The ability to specify a display width of N (use without N).
•The --default-character-set and --default-collation server options (use --character-set-server and --collation-server).
•The --delay-key-write-for-all-tables server option (use --delay-key-write=ALL).
•The --enable-locking and --skip-locking server options (use --external-locking and --skip-external-locking).
•The --log-bin-trust-routine-creators server option (use --log-bin-trust-function-creators).
•The --log-long-format server option.
•The --log-update server option.
•The --master-xxx server options to set replication parameters (use the CHANGE MASTER TO statement instead): --master-host, --master-user, --master-password, --master-port, --master-connect-retry, --master-ssl, --master-ssl-ca, --master-ssl-capath, --master-ssl-cert, --master-ssl-cipher, --master-ssl-key.
•The --safe-show-database server option.
•The --skip-symlink and --use-symbolic-links server options (use --skip-symbolic-links and --symbolic-links).
•The --sql-bin-update-same server option.
•The --warnings server option (use --log-warnings).
•The --no-named-commands option for mysql (use --skip-named-commands
•The --no-pager option for mysql (use --skip-pager).
•The --no-tee option for mysql (use --skip-tee).
•The --position option for mysqlbinlog (use --start-position).
•The --all option for mysqldump (use --create-options).
•The --first-slave option for mysqldump (use --lock-all-tables).
•The --config-file option for mysqld_multi (use --defaults-extra-file).
•The --set-variable=var_name=value and -O var_name=value general-purpose options for setting program variables (use --var_name=value).
•The --with-pstack option for configure and the --enable-pstack option for mysqld.
ldb2741 2011-01-24
- 打赏
- 举报
板凳
ACMAIN_CHM 2011-01-24
- 打赏
- 举报
mysqldbd 2011-01-24
- 打赏
- 举报
[Quote=引用 10 楼 mr_mablevi 的回复:]
引用 8 楼 mysqldbd 的回复:
引用楼主 mr_mablevi 的回复:
以为要年后升星的,提前了一个星期,o(∩_∩)o ..发不了300分的帖子,用200分代替
在mysql版里学到很多,特别感谢:
ACMAIN_CHM,zuoxingyu,iihero,wwwwb等这些人的指点.新的一年,继续努力;
PS:
顺便带个mysql的问题:
打算玩下mysql5.5 不……
[/Quote]
我是开玩笑的了，嘻嘻，谢谢了! 新年快乐，我27号就从上海回老家过年了，没有几天了，祝贺大家新年快乐！
引用 8 楼 mysqldbd 的回复:
引用楼主 mr_mablevi 的回复:
以为要年后升星的,提前了一个星期,o(∩_∩)o ..发不了300分的帖子,用200分代替
在mysql版里学到很多,特别感谢:
ACMAIN_CHM,zuoxingyu,iihero,wwwwb等这些人的指点.新的一年,继续努力;
PS:
顺便带个mysql的问题:
打算玩下mysql5.5 不……
[/Quote]
我是开玩笑的了，嘻嘻，谢谢了! 新年快乐，我27号就从上海回老家过年了，没有几天了，祝贺大家新年快乐！
谁学逆向工程 2011-01-24
- 打赏
- 举报
5.5有精神病。 5.1有点乱码
mysqldbd 2011-01-24
- 打赏
- 举报
[Quote=引用 13 楼 apple_8180 的回复:]
恭喜！
[/Quote]
大侠来了啊，膜拜一下！
恭喜！
[/Quote]
大侠来了啊，膜拜一下！
wcqqq 2011-01-24
- 打赏
- 举报
祝大家新年快乐！！！++++++ 接分ing
shyokou 2011-01-24
- 打赏
- 举报
个人最喜欢的就是 InnoDB 的完善和成默认啦, 别的方便譬如性能上体会不明显 ...
[Quote=引用楼主 mr_mablevi 的回复:]
以为要年后升星的,提前了一个星期,o(∩_∩)o ..发不了300分的帖子,用200分代替
在mysql版里学到很多,特别感谢:
ACMAIN_CHM,zuoxingyu,iihero,wwwwb等这些人的指点.新的一年,继续努力;
PS:
顺便带个mysql的问题:
打算玩下mysql5.5 不知道 和5.1的差距有多大,(网上说差距甚大)用过有体会的人发表下看法;
[/Quote]
[Quote=引用楼主 mr_mablevi 的回复:]
以为要年后升星的,提前了一个星期,o(∩_∩)o ..发不了300分的帖子,用200分代替
在mysql版里学到很多,特别感谢:
ACMAIN_CHM,zuoxingyu,iihero,wwwwb等这些人的指点.新的一年,继续努力;
PS:
顺便带个mysql的问题:
打算玩下mysql5.5 不知道 和5.1的差距有多大,(网上说差距甚大)用过有体会的人发表下看法;
[/Quote]
加载更多回复（3）
