MySQL Bugs: #39631: mysql version clarification

Bug #39631	mysql version clarification
Submitted:	24 Sep 2008 17:28	Modified:	2 Oct 2008 8:12
Reporter:	vijay bhasker	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	Instance Manager	Severity:	S2 (Serious)
Version:	5.0.68	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	Please give solution to this bug

Description:
what version of mysql community edition is equivalent to mysql enterprise Version 5.0.68

How to repeat:
what version of mysql community edition is equivalent to mysql enterprise Version 5.0.68

Suggested fix:
what version of mysql community edition is equivalent to mysql enterprise Version 5.0.68

There are no direct relationship. Please read at http://dev.mysql.com/doc/refman/5.0/en/installation-overview.html about difference between these 2 servers. But answer to your question: version closest to release of 5.0.68 which is 5.0.67.

Thank u sweta for you fast response,but communtiy edition is different compared to enterprise server edition. YOu are telling about the previous edition of 5.0.68, but the want exactly equivalent to mysql enterprise version 5.0.68 

           I want exactly what version of mysql community edition is equivalent to mysql enterprise Version 5.0.68

Thank you, vijay, for the answer.

There is not such a version.

ThanQ sweta for your update, please give me a solution for this.

         Here in our project we are using server edition 5.0.68, so we want the community edition which is having the same features as in server edition. So that we can reduce the cost. So could you please sugget us any other alternative to reduce the  cost, if following features are not available. We want to reduce the cost in our project.

I want to know the features, compatibility of 5.0.68 Enterprise edition with 5.0.67 Community edition. I want the exact difference between these two editions and compatibity features in both.

Thanks in Advance.

Short outage on 10/04(Saturday) at 6 AM EST to recycle mysql_p021 instance (useclpcll636db1 64.210.192.206) as one of connections on MYSTATS has gone into killed state and requires a recycle of instance to force off this connection (we tried killing it, but it didnt work). 

            So what to do for resolving this issue.

Short outage on 10/04(Saturday) at 6 AM EST to recycle mysql_p021 instance (useclpcll636db1 64.210.192.206) as one of connections on MYSTATS has gone into killed state and requires a recycle of instance to force off this connection (we tried killing it, but it didnt work). 

            So what to do for resolving this issue.

We're sorry, but the bug system is not the appropriate forum for asking help on using MySQL products. Your problem is not the result of a bug.

Support on using our products is available both free in our forums at http://forums.mysql.com/ and for a reasonable fee direct from our skilled support engineers at http://www.mysql.com/support/

Thank you for your interest in MySQL.

Please also read at http://dev.mysql.com/doc/refman/5.0/en/instance-manager.html: "MySQL Instance Manager is been deprecated in MySQL 5.1 and is removed in MySQL 6.0."