Author Topic: Migration from Oracle to MySQL: CLOB vs. text  (Read 2958 times)

RudiCz

  • EA Novice
  • *
  • Posts: 11
  • Karma: +1/-0
    • View Profile
Migration from Oracle to MySQL: CLOB vs. text
« on: February 24, 2016, 07:19:27 pm »
Hi,
we are migrating our EA-Oracle-repository to MySQL. We have problems transferring ORACLE-CLOB-attributes to MySQL-text-attributes:
CLOB-size is 4GB; Text-size is 64 KB
Why are these attributes defined in the MySQL-Schema with type 'text'? In our opinion 'longtext' (=4GB) would be the correct type.
Is it possible to change the affected attributes from 'text' to 'longtext' in the MySQL-Schema.sql-file without side-effects?
Thanks!
Kind regards,
Rudi

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 8554
  • Karma: +209/-26
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Migration from Oracle to MySQL: CLOB vs. text
« Reply #1 on: February 24, 2016, 07:40:39 pm »
Rudi,

You could change the data schema, but that doesn't seem like a very good idea. I'm pretty sure EA won't really object, but it makes things harder when transferring to other models etc..
Are you using the standard model transfer feature to transfer the model?
In that case you should not run into trouble. If you do I would suggest to contact Sparx support.

Geert

RudiCz

  • EA Novice
  • *
  • Posts: 11
  • Karma: +1/-0
    • View Profile
Re: Migration from Oracle to MySQL: CLOB vs. text
« Reply #2 on: February 24, 2016, 08:15:33 pm »
Hi Geert,
for transfer I use the standard model feature (Project | Data Management | Project Transfer | DBMS to DBMS). Without changing the MySQL-type from 'text' to 'longtext' the transfer reports error:
'Data too long for column 'Script' at row 1 [Select * from t_script] Field: script.'
OK, I will ask Sparx directly for side-effects.
Thanks
Rudi