From: Frazer Clement
Date: February 2 2009 11:18am
Subject: Re: what's the reason for problem "Tuple did not exist"?
List-Archive: http://lists.mysql.com/ndb-connectors/664
Message-Id: <4986D680.4060003@sun.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
Content-Transfer-Encoding: 7BIT

Hi Tarbin,
  Can you explain a bit further what you are doing?
  FYI : TEXT *is* a BLOB with a character set.  So you must use the BLOB 
API to read/write TEXT columns.  You *must not* use the normal 
setValue/getValue API for TEXT columns.
  Perhaps you could describe what does and does not work in terms of 
schemas, your code and the content and length of the data you are using.
Frazer

tarbin jiang wrote:
> all,
> when I insert a record which including a TEXT type column, it returns error: 
> com.mysql.cluster.ndbj.NdbApiPermanentException: Tuple did not exist.
> I found that if I set the TEXT type column as a formal string, it works without error.
> but if I set the Text type column as a xml file, the error pops.
> The procedure of reading xml file is no problem. And I used NDBBlob type to handle text type.
>  
> insertOperation.setValue(xmlFile.bytes())
>  
> can anybody help me?
> thanks from tarbin
>  
> _________________________________________________________________
> News, entertainment and everything you care about at Live.com. Get it now!
> http://www.live.com/getstarted.aspx
>
>   

-- 
Frazer Clement, Software Engineer, MySQL Cluster 
Sun Microsystems - www.mysql.com
Office: Reading, UK

Are you MySQL certified?  www.mysql.com/certification