Error Transfering model from Database

[jguerra]

Hi,
I was trying to transfer a project from the database repository to an .eap file and I got this error:

Transfer Error

An Error has ocurred: DAO.Recordset[3314]
The filed 't_umlpattern.PatternXML' can't contain a Null value because the Required property for this filed is set to True. Enter a vlaue in this field.
[Select * from t_umlpattern]
Field: version

Database repository is MySQL
EA version 7.1 b833

On EA 7.1 b828 works fine!

Does anyone an idea whether it is a bug on b833 or something???

Thanks

[Thomas Mercer-Hursh]

I see this error transferring from OpenEdge to EAP because the OpenEdge has character (up to 32KB) and CLOB datatypes (which EA can't use) and when one creates the original project, t_umlpattern contains a number of records with memo datatype which are greater than 32K.  So, those end up being null.  You can get rid of the error by going through and changing the null to blank.  I don't know the MySQL datatypes, but I'll bet it is the same thing.

Oh, and it doesn't matter unless you are trying to use one of those patterns.

[jguerra]

Hi Thomas,
Thanks for shedding some light on this.

What bothers me now is wthether this is "issue" on the database schema or in the application. By this i mean, the repository was created a year ago, so I am not sure right now whether the sql scripts have been changed since then and I'd need an upgrade of the database and so on so forth ...

[Thomas Mercer-Hursh]

If you have been using the repository successfully, then I wouldn't worry about the schema.  I had some issues when I first built mine with the Sparx schema containing SQL datatypes which didn't map very well to OpenEdge data types, but this is a different issue.  With t_umlpattern, the problem is just that there is a fundamental mismatch.  If you still had the log from when you did the original transfer, you would probably find the error in there.  There isn't really anything to do unless Sparx can start supporting CLOB datatypes or whatever the equivalent is for you.  But, it is also something that doesn't really matter, except for the annoying error messages, unless you want to use those patterns.  Change the nulls to blanks and the error messages go away, but of course the patterns are still missing.

[jguerra]

Thanks Thomas. I basically ignored the error as you pointed out, so I moved on and I continued modeling with 7.1 b833 against our database repository. So, eventually i dumped again the database repository onto an eap file and the error is gone!. I tried several times and the model was transferred successfully with no errors.
AFAIK, the repository hadn't had been touched with b833 until I did it. so, not sure whether there is a link with this, but no more errors so far !!!

[«Midnight»]

When did you create your repository?

I have had situations in the past - not recently, but then again I have not had to create new repositories often of late - where my scripts seemed to be out of date. Even though I did not find any obvious differences - based on a quick scan, not a detailed inspection - between old and new scripts, I found that downloading the scripts anew solved mysterious problems. I last noticed this around the time of EA 7.0 in a SQL Server environment with network-based servers. I was able to create repositories without issue, but nothing worked when I tried to get a model working with them. They seemed OK when I looked at them though. Starting over from scratch with newly-downloaded scripts made the problems disappear.

I'm sorry I cannot be more specific. At the time it was far more important to clear the hurdle and get things working than to diagnose the problem. Once it went away we just upgraded everything, transferred the models, and never looked back.

HTH, David

[Thomas Mercer-Hursh]

For my part, I think I am using the most recent scripts since it was my feedback on issues with the prior ones which resulted in them being changed.

[jguerra]

The Repo in question was created six-seven months ago. Scripts were downloaded before but I can't find out exactly when was it. Apparently Sparx doesn't version MySQL scritps, it looks like the scripts were created on 2002, but I am not sure whether they have been changed since. All I found at the sparx web site regarding to the version of the current scripts was this comment at the begining of the sql file.

Code: [Select]

/*
MySQL Backup
Source Host:           localhost
Source Server Version: 4.0.4-beta-max-nt
Source Database:       basemodel
Date:                  2002/11/05 14:39:05
*/The news is on b833 the transfer fails in one particular model, the Technology model !!!. We have six models on database repository and the transfer fails only on the model it contains our UML profiles.
This is what the error log file looks like!

...
Copying project information for: t_attributeconstraints
Copying project information for: t_umlpattern
ERROR: *** t_umlpattern - record no: 12
Copying project information for: t_version
Copying project information for: t_xref
...

So, yes the error is still on !!

[Thomas Mercer-Hursh]

So, did you look in t_umlpattern for nulls?  Have you checked the relative size of the datatypes?

[jguerra]

It seems to me that the problem is on the PatternXML column or how the application handle this table/column.
Yes, there are 23 records on that table (t_umlpattern) and the record 12 is the only one that the column PatternXML is in blank (Sixth position on the output below).  It could be possible that the application didn't fill it in properly or something, but I am not sure. Question for the guys at sparx, this is too low level stuff for me anyway!!

"12"      "GoF Creational Patterns"      "Abstract Factory"      "NULL"      "This pattern provides an interface for creating families of related or dependent objects without spe..."      ""      "2.0"

Regarding the other 22 records, the column got something like this..

<?xml version="1.0"?><XMI xmi.version="1.1" xmlns:UML="omg.org/UML1.3" timestamp="2004-12-17 15:12...

[«Midnight»]

Send this in as a bug report directly to Sparx. Use the Report a Bug link, below the Support link near the bottom of any forum page. If you are a registered user, follow the appropriate link on the resulting page, or go to the Registered Users page (by clicking the link at the top of any forum page) and follow the directions there. The registered version of the bug report allows you to attach sample files. Perhaps you could zip up your project and XML file and send those.

While the Sparxians are very active participants here, this is a user forum. The best way to bring these issues to Sparx' attention is via a 'real' bug report.

This looks like something important. If there is an error in EA, or even a significant vulnerability - where EA mishandles a common defect - then Sparx will want to know. They tend to be quite responsive to such reports.

David

[jguerra]

I reported the issue to Sparx and we'll see if the can find out quickly whats going on and whether or not is a bug anyway!

thanks!