Book a Demo
« previous next »
Pages: [1]

Author Topic: "Value too large" when importing XMI  (Read 5718 times)

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
"Value too large" when importing XMI
« on: August 05, 2007, 09:49:09 pm »
Hi,

Another one on the XMI import/export.
When exporting an object to XMI (EA xmi export) that has a tagged value, I get an error importing that same XMI file.
This only seems to be happening when you have special characters in the tagged value (tabs, CR-LF,???) and when the total of 255 charachters is used in the tagged value.
I tested this with a plain '123456...' and that was fine.
Tested with the text:
Quote
Er wordt een nieuw mfa record aangemaakt met invulling van de volgende velden
MFA-TYPEA037
MFA-USERID'DISTRI'
MFA-DATVANA037.Debug_message
MFA-DATTOTA037.Fin_message
MFA-DATRECsysteemdatum
MFA-TYPERECORDA037.Type de record
MFA-ANOMALIEA037.C


and when trying to import the xmi I got a database error: "ORA-12899: value too large for column "D00ARCH01"."T_OBJECTPROPERTIES"."VALUE" (actual: 262, maximum: 255)"
I'm very worried about this since the version control add-ins use this xmi import/export principle; and i'm afraid it is going to be a problem there too. (I'm testing version control integration in the next weeks)

I'll be submitting a bug report for this issue.
Logged

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: "Value too large" when importing XMI
« Reply #1 on: August 06, 2007, 08:52:28 pm »
Another quick reply from our friends at Sparx support.
Quote
Hello Geert,

Thanks for the note and the sample XMI file.

This is a bug and I have lodged it for further investigation with the
following details :

Issue ID : 07081169
Description : Database error when adding tags whose value exceed 255
characters during an XMI 2.1 import

We will have this issue fixed for the next Build of EA.

Hope this resolves your issue. Thank you for your patience and support.
If you have any further queries, feel free to write-in.
Logged

Dave_Bullet

  • EA User
  • **
  • Posts: 295
  • Karma: +0/-0
    • View Profile
Re: "Value too large" when importing XMI
« Reply #2 on: August 07, 2007, 02:22:44 pm »
Geert,

you can fix this by increasing the length of the value column in the database for the t_objectproperties table.

Depending on which DB you are using, I may be able to provide the SQL.

Cheers,
DAvid.
Logged
"I know I'm close to a good design, but it's like the balloon animals, squeeze in one spot and the problem moves down the line"

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: "Value too large" when importing XMI
« Reply #3 on: August 07, 2007, 08:36:51 pm »
Thanks David, the thought crossed my mind as well, but I don't think that is really a viable option.
Changing the database schema could possibly mean support- and upgrade nightmares.
Logged

Dave_Bullet

  • EA User
  • **
  • Posts: 295
  • Karma: +0/-0
    • View Profile
Re: "Value too large" when importing XMI
« Reply #4 on: August 08, 2007, 01:58:11 pm »
Upgrade nightmares? - No - it doesn't.  I've never had an issue with the EA UI when increasing lengths of tagged value fields (ie. Mine are each 3,200 long and I have some large > 1000 characters).

EA hasn't changed its database model since I think V3.5? - so you are pretty safe.

As far as adding columns to EA base tables - then you are correct - I do not recommended that.  you are better to add your own tables and join on EA IDs.  Reason being - EA does a lot of "select *" which breaks EA :-(

David.
Logged
"I know I'm close to a good design, but it's like the balloon animals, squeeze in one spot and the problem moves down the line"

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: "Value too large" when importing XMI
« Reply #5 on: August 08, 2007, 03:36:56 pm »
The good news is:
Quote
EA hasn't changed its database model since I think V3.5? - so you are pretty safe.


The BAD news is:
Quote
EA hasn't changed its database model since I think V3.5? - so you are pretty safe.


;)

Paolo
Logged
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Dave_Bullet

  • EA User
  • **
  • Posts: 295
  • Karma: +0/-0
    • View Profile
Re: "Value too large" when importing XMI
« Reply #6 on: August 08, 2007, 05:17:24 pm »
Off topic apologies...

Hey Paolo...

you should get a load of some of the business databases I have to support....  We use an RDBMS as a flat file system... I always get this from developers "but we have to copy the values we need from table A into table B, because they are not in table B"... and this is an OLTP system....

:)
Logged
"I know I'm close to a good design, but it's like the balloon animals, squeeze in one spot and the problem moves down the line"

thomaskilian

  • Guest
Re: "Value too large" when importing XMI
« Reply #7 on: August 09, 2007, 07:09:40 am »
Isn't it possible to fire someone that is obviously incompetent? :-X
Logged

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: "Value too large" when importing XMI
« Reply #8 on: August 30, 2007, 09:46:00 pm »
Tested on build 816 and it is fixed!
Logged
Pages: [1]
« previous next »