Data too long for column with MySQL

[genjide]

I've searched the forum about this but I found nothing.

So, here is the problem :

When I want to transfer my EAP project into my MySQL database,  I've got the error message

[MySQL][ODBC 3.51 Driver][mysqld-5.0.41-community-nt]Data too long for column 'PatternXML' at row 1
[Select * from t_umlpattern]
Field: version

The data take a little less 30.000 characters, mysql seems to not support this number.

I've checked into the table and in this column ('PatternXML') I have only the first xml markup : <?xml version="1.0"?>

I've ran the transfer into an SQLServer2005 database, and there is no problem.

So is there a solution to that problem, or I can work on my mysql database without problems...?

Thanks in advance.

[«Midnight»]

First, make sure you've got the most recent build of EA. At this time it is build 815, wtih 816 coming out any day.

Next, bring down the most recent script for generating a MySQL database from the Sparx site. There may have been tweaks since you last downloaded it.

If that does not work, submit a bug report to Sparx directly - do this ASAP, so that the correction can be made in time for build 817.

Search my recent posts for our current best practice on how to handle bug reports and feature requests.

HTH, David

[thomaskilian]

I once had problems tranferring "non-standard" things like patterns. I deleted them from the original model, transferred then without problems and re-imported the stuff. Not sure whether that will help. Else report a bug to Sparx.

[KP]

I overheard something about this last week. I don't know any of the details (i.e. what the maximum size is, what DBMS are affected, whether anyone is working on a fix) but the suggested work-around was to edit the pattern's XML file in a text editor, remove the preview image, save and reimport into your EA model. The preview image is nice to have but also potentially quite large...

[genjide]

Now that's working... In fact, I've tried too change the datatype of the field in "longtext", but mysql didn't want to accept the change (don't know why). I have reinstalled all the stuff (with latest builds) and the problem is gone.