MySQL Bugs: #11786: MySQL Cluster changes in 5.0: Limit On Number of Metadata Objects?

Bug #11786	MySQL Cluster changes in 5.0: Limit On Number of Metadata Objects?
Submitted:	6 Jul 2005 22:06	Modified:	29 Mar 2006 2:07
Reporter:	Ian Neubert	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S4 (Feature request)
Version:		OS:
Assigned to:	Jon Stephens	CPU Architecture:	Any

Description:
Was the Limit On Number of Metadata Objects increased, as expected in MySQL 5.0.6-beta? The documentation still says that it is hoped to be implemented in 5.0.6-beta, however 5.0.7-beta is now out.

How to repeat:
Last bullet on:
http://dev.mysql.com/doc/mysql/en/mysql-5-0-cluster-changes.html

Serge worked on this. He should be able to provide the information needed.
Thanks
JBM

Could you give more information about your issues?

I'm just wondering if the 5.0.6-beta did include the increase in the number of allowed objects. The documentation says that it is "hope"ed to be implented.

I am only requesting the manual be updated to reflect if this did occur, or to be rewritten so it shows whats going on, and not what's hopped to happen in the future.

Thank you for your bug report. This issue has been addressed in the
documentation. The updated documentation will appear on our website
shortly, and will be included in the next release of the relevant
product(s).

Additional info:

http://dev.mysql.com/doc/refman/5.0/en/mysql-5-0-cluster-changes.html was already updated quite some time ago to read: "In MySQL 4.1, each Cluster database may contain a maximum of 1600 metadataobjects, including database tables, system tables, indexes and BLOB values. Beginning with MySQL 5.0.6, this number is increased to 20320."

(I've just reworded this in a way that I hope makes things absolutely clear.)