Bug #34930 NdbRecord object not valid between cluster connections

Submitted:	28 Feb 2008 14:26	Modified:	19 Jan 2016 13:05
Reporter:	Frazer Clement	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Cluster: NDB API	Severity:	S3 (Non-critical)
Version:	mysql-5.1-telco-6.2	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
An NdbRecord design goal is for an NdbRecord object to be reusable between threads and at any time until the user is finished with it.
The current NdbRecord implementation embeds an NdbTableImpl*, which points to data which is not independent of the ndb_cluster_connection it was created using.
This means that users must discard/rebuild their NdbRecord objects when deleting an ndb_cluster_connection, which is not documented anywhere.

How to repeat:
Create cluster connection.
Connect to cluster.
Create table.
Obtain default NdbRecord from table object,
Use for PK access.

delete cluster connection.
Create cluster connection.
Connect to cluster.
Attempt to use NdbRecord from above for PK access.

Suggested fix:
NdbRecord should be changed to be truly independent of any ndb_cluster_connection, or subtended object.

still verified

kr
Bogdan Kecman

Page generated in 0.040 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.