Hi all,
In the hhr/complexAttributes branch (qvtd
git on eclipse) you can find the QVTiEvaluationVistor that
works with the UML2RDBMS example.
Some tweaks of the transformation
(ClassToRDBMSSchedule.qvti) where done in order to, in my
opinion, correctly transform UML to RDBMS based on my
understanding of the QVTc example in the QVT specification.
There is an issue, at least as I see it now
regarding classes with complex attributes. If Class A has a
complex attribute b of Type B, and Class B, then the table for
A must have 1 column for each of the attributes of class B. If
B has a complex attribute c of Type C, then A should also have
1 column for each of the attributes of class C, and so on and
so forth.
Currently the
ComplexAttributeComplexAttributes mapping is called from
mapping ClassToTableLM, and thus the required recursive dive
through all the complex attributes is not correctly done. It
would be simple to move the ComplexAttributeComplexAttributes
to the PackageToSchema mapping and then visit all the
attributes of all the classes to guarantee the full depth
visit. However, the current analysis for identifying this
special cases is not fully developed. Further research will
help us understand this issues.
Regards,
Horacio Hoyos Rodríguez
EngD Student
University of York
http://www.york.ac.uk/docs/disclaimer/email.htm