呵呵,什么时候出来,谁也不知道, 等待吧, 不过看它的说明, 还是值得等待的噢!http://www.mysql.com/doc/en/TODO_MySQL_5.0.html1.9.2 New Features Planned For 5.0The following features are planned for inclusion into MySQL 5.0. Note that because we have many developers that are working on different projects, there will also be many additional features. There is also a small chance that some of these features will be added to MySQL 4.1. For a list what is already done in MySQL 4.1, see section 1.6.1 Features Available From MySQL 4.1. For those wishing to take a look at the bleeding edge of MySQL development, we have already made our BitKeeper repository for MySQL version 5.0 publically available. See section 2.3.4 Installing from the Development Source Tree. Stored Procedures (！ Oracle 过来的用户有福了) Stored procedures are currently being implemented. This effort is based on SQL-99, which has a basic syntax similar (but not identical) to Oracle PL/SQL. We will also implement the SQL-99 framework to hook in external languages, and (where possible) compatibility with, for example, PL/SQL and T-SQL. New functionality Elementary cursor support. (初步的游标支持)
Visible RTREE index for MyISAM tables. In 4.1 RTREE indexes are used internally for geometrical data, but not directly usable. Dynamic length rows for HEAP tables. Standards compliance, portability and migration Add true VARCHAR support (there is already support for this in MyISAM). Speed enhancements SHOW COLUMNS FROM table_name (used by mysql client to allow expansions of column names) should not open the table, only the definition file. This will require less memory and be much faster.
Allow DELETE on MyISAM tables to use the record cache. To do this, we need to update the threads record cache when we update the `.MYD' file.
Better in-memory (HEAP) tables: Dynamic size rows. Faster row handling (less copying). Internationalisation When using SET CHARACTER SET we should translate the whole query at once and not only strings. This will enable users to use the translated characters in database, table, and column names. Usability enhancements Resolving the issue of RENAME TABLE on a table used in an active MERGE table possibly corrupting the table.
to shuixin13(犬犬（心帆）) ： 用过postgresql和sap db吗？他们都已经有Stored Procedures！
它会支持stored procedure吗？
等待吧,
不过看它的说明,
还是值得等待的噢!http://www.mysql.com/doc/en/TODO_MySQL_5.0.html1.9.2 New Features Planned For 5.0The following features are planned for inclusion into MySQL 5.0. Note that because we have many developers that are working on different projects, there will also be many additional features. There is also a small chance that some of these features will be added to MySQL 4.1. For a list what is already done in MySQL 4.1, see section 1.6.1 Features Available From MySQL 4.1. For those wishing to take a look at the bleeding edge of MySQL development, we have already made our BitKeeper repository for MySQL version 5.0 publically available. See section 2.3.4 Installing from the Development Source Tree. Stored Procedures (！ Oracle 过来的用户有福了)
Stored procedures are currently being implemented.
This effort is based on SQL-99,
which has a basic syntax similar (but not identical) to Oracle PL/SQL.
We will also implement the SQL-99 framework to hook in external languages,
and (where possible) compatibility with, for example, PL/SQL and T-SQL. New functionality
Elementary cursor support. (初步的游标支持)
Visible RTREE index for MyISAM tables.
In 4.1 RTREE indexes are used internally for geometrical data,
but not directly usable. Dynamic length rows for HEAP tables. Standards compliance, portability and migration
Add true VARCHAR support (there is already support for this in MyISAM). Speed enhancements
SHOW COLUMNS FROM table_name
(used by mysql client to allow expansions of column names)
should not open the table, only the definition file.
This will require less memory and be much faster.
Allow DELETE on MyISAM tables to use the record cache.
To do this, we need to update the threads record cache
when we update the `.MYD' file.
Better in-memory (HEAP) tables:
Dynamic size rows.
Faster row handling (less copying). Internationalisation
When using SET CHARACTER SET
we should translate the whole query at once and not only strings.
This will enable users to use the translated characters
in database, table, and column names. Usability enhancements
Resolving the issue of RENAME TABLE
on a table used in an active MERGE table possibly corrupting the table.
用过postgresql和sap db吗？他们都已经有Stored Procedures！