Bug #53577 | usage count for ndb_init()/ndb_end() count | ||
---|---|---|---|
Submitted: | 11 May 2010 17:09 | Modified: | 25 Jun 2010 14:27 |
Reporter: | Hartmut Holzgraefe | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Cluster: NDB API | Severity: | S4 (Feature request) |
Version: | mysql-telco-7.0, any | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[11 May 2010 17:09]
Hartmut Holzgraefe
[11 May 2010 19:23]
Jonas Oreland
is it worth it, given that the method is not even thread safe? why not simply do it in their application?
[25 Jun 2010 14:27]
Hartmut Holzgraefe
If not for anything else then at least for consistency between ndb_init() and ndb_end(). Having one doing a check while the other doesn't ... well ... This is also not only a multi-thread issue, it is also going to bite in single threaded applications where two independent, optional components make use of NDBAPI. Having proper reference counting on init/end invocations is a must there even without the calls being mutex protected.