MySQL Forums
Forum List  »  NDB clusters

Identifying unmatched rows in batched queries
Posted by: Martin Plumley
Date: May 05, 2006 09:01AM

Hi All

We are developing an application for a MySQL cluster and are accessing the database using the NDB API. For performance reasons we wish to batch up as many operations as possible under a single NdbTransaction::execute.

However, we can't find an easy way to identify which operation has returned no match. Using getNdbError, the "Tuple doesn't exist" error is part of the transaction and the operation doesn't have any error. So which operation(s) found no matching row? We need to know which operations find no match under a given transaction.

The getValue method returns a NdbRecAttr but there is no way of initialising this to see if it is unchanged following the execute. Is there some method we don't know about? Are we missing something obvious?

Any suggestions gratefully received.

Thanks

Martin

Options: ReplyQuote


Subject
Views
Written By
Posted
Identifying unmatched rows in batched queries
1491
May 05, 2006 09:01AM


Sorry, you can't reply to this topic. It has been closed.

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.