Skip navigation links

MySQL Forums :: Cluster :: Errors saving to BLOB via ClusterJ


Advanced Search

Re: Errors saving to BLOB via ClusterJ
Posted by: Jacek Furmankiewicz ()
Date: March 09, 2012 09:51AM

Interesting twist. We changed F_VALUE To TEXT and then MEDIUMTEXT and the entity to String instead of byte[]

Now we get a different error telling us it can only accept 256 char strings...ona MEDIUMTEXT field?


| T_SUBSCRIBER_CACHE | CREATE TABLE `T_SUBSCRIBER_CACHE` (
`F_KEY` varchar(255) COLLATE utf8_bin NOT NULL,
`F_VALUE` mediumtext COLLATE utf8_bin NOT NULL,
`F_LASTMODIFY_TIME` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
PRIMARY KEY (`F_KEY`)
) ENGINE=ndbcluster DEFAULT CHARSET=utf8 COLLATE=utf8_bin |


com.mysql.clusterj.ClusterJUserException: Data length 275 too long. Column F_VALUE can only accept data of length 256.

Is this a ClusterJ bug?

Options: ReplyQuote


Subject Views Written By Posted
Errors saving to BLOB via ClusterJ 1329 Jacek Furmankiewicz 03/09/2012 09:23AM
Re: Errors saving to BLOB via ClusterJ 690 Jacek Furmankiewicz 03/09/2012 09:51AM
Re: Errors saving to BLOB via ClusterJ 813 Craig Russell 03/09/2012 03:19PM
Re: Errors saving to BLOB via ClusterJ 709 Jacek Furmankiewicz 03/16/2012 01:41PM
Re: Errors saving to BLOB via ClusterJ 683 Craig Russell 03/21/2012 09:18AM


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.