MySQL Bugs: #32185: DropDDObjects in testDict.cpp sees the ndb tables in mysql as user and fails

Bug #32185	DropDDObjects in testDict.cpp sees the ndb tables in mysql as user and fails
Submitted:	8 Nov 2007 14:10	Modified:	7 Apr 2014 13:05
Reporter:	Jonathan Miller	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	Tests: Cluster	Severity:	S7 (Test Cases)
Version:	mysql-5.1-telco-6.2	OS:	Linux
Assigned to:	Magnus Blåudd	CPU Architecture:	Any
Tags:	mysql-5.1-new-ndb, mysql-5.1-telco-6.*

Description:
DropDDObjects in testDict.cpp sees the ndb tables in mysql as user and fails.

These tables should be listed as system tables, but there is a disagreement on that. 

So to fix the problem currently DropDDObjects should ignore ndb_apply_status, NDB$BLOB_2_3 and ndb_schema

How to repeat:
run testDict test cases that use DropDDObjects

Suggested fix:
So to fix the problem currently DropDDObjects should ignore ndb_apply_status, NDB$BLOB_2_3 and ndb_schema

http://lists.mysql.com/commits/37335

Approved by Tomas, pushed into new-ndb merged -> telco-6.2 -> telco-6.3

Could you give some more info what "and fails..." mean. How? Error message?

Is the disagreement really about whether those tables should be marked as system table or about whether they should be visible at all?

Doe not seem so nice if we need to hack every program to know about those tables. Better if NdbDictionary could tell us that it is a system table and skip it. Or mark them as "hidden"? I.e something inbetween user and system tables.

The problem with these tables are that they are not really system tables to NDB, they are user tables created by the specific implementation of "MySQL Server". ;)

Why limit drop of NDB$BLOB_2_3 ? Try to create another table with blobs from mysqld and you'll see another blob table.

Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php

If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.