[kepler-users] Provenance Recorder Error!

[Derik Barseghian]

Hi Joseph,
This is an issue Dan came across w/ mysql too, and there's currently a note in the code to fix it. It doesn't seem to affect hsql. The column should be defined as 255 chars now (you can see the definition in Column.java); he guesses hsql doesn't enforce this size hence the issue not happening with the default provenance store. I've counted one module_dependency list as being 389 characters. Yes, changing the size of that column should fix the issue. I would change to at least VARCHAR(500). We'll fix this for the next provenance module release.

Derik

On Jan 27, 2011, at 12:01 PM, Josep Maria Campanera Alsina wrote:

> Dear all,
> I've found this error when testing Kepler 2.1 (in Mac 10.6 and Mysql
> 5.2.31) with R-·D_plot.xml workflow in
> KeplerData/workflow/module/r-2.1.0/demos/R. This error prevents me to
> go further with Kepler right now since I cannot execute any workflow
> with the Provenance recorder turned on. The installation was fine!
> 
> "ptolemy.kernel.util.IllegalActionException: RecordingException:
> com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for
> column 'module_dependencies' at row 1 in
> .ProvenanceRecorder_Example_1.TOP Provenance Recorder"
> 
> Do I have to change the definition of the variable
> "module_dependencies" in MySQL database, VARCHAR(100) or longer? Or
> this is related to other issues? I haven't found any discussion in the
> list. Any clue?
> 
> Congratulations for the new version of Kepler, it really seems an step forward!
> 
> Campa,
> _______________________________________________
> Kepler-users mailing list
> Kepler-users at kepler-project.org
> http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users