Messages

1

Suggestions and Requests / Re: Compound Unique Constraints in Data Model

« on: May 04, 2010, 09:42:42 pm »

As of today, multiple fields in the same PIM Table can be tagged and a transformation can extract the right set for the operation and parameter elements in the PSM.

It works

2

Suggestions and Requests / Compound Unique Constraints in Data Model

« on: October 28, 2008, 06:46:32 pm »

Hello,
I would like to model compound uniqe constraint and cannot see how to do that in EA. Is it not possible, if so, could it be added in a future version?

If it is possible to create compound unique constraints, how do I invoke it from MDA Style DDL Transformation? I do have the tokens for Primary and Foreign Key, but there is no Unique for a compound.

If someone shares my opinion or even has a workaroung, please let me know.
Thx.
Peter

3

Suggestions and Requests / Compound Unique Constraints in Data Model

« on: July 21, 2009, 05:40:45 pm »

Hello,
I would like to model compound uniqe constraint and cannot see how to do that in EA. Is it not possible, if so, could it be added in a future version?

Greetings
Peter

4

Suggestions and Requests / MDA style transformations with compound unique key

« on: July 21, 2009, 05:44:22 pm »

Hello,
I would like to model compound uniqe constraint in a PIM. What would I have to use in the PIM to get enough information to let a MDA style transformation create the compound keys on the PSM and than on the DDL. Is it not possible, if so, could it be added in a future version?

Greetings Peter

5

General Board / MDA Transformation driving if PK is clustered

« on: February 18, 2015, 03:13:26 am »

I use transformations to convert a PIM into something rather physical that is ment to ddl code generate. I wonder what tag or element or whatever i can use in the Transformation to create a non clustered PK. Thanks for any help

6

General Board / Re: How to set a columns to UNIQUE (MSSQL)?

« on: January 12, 2011, 03:11:25 am »

Please have a look at this if you are still interested in MDA Transformas for Unique and NotNull: unique is set as tag on the attribute


----------------------------------------------------
this is a response to a support question I asked months ago:
Thank you for your enquiry.

In addition to setting the "unique" property to the column you also need
to create a stereotyped operation to fully define the unique constraint
in your transformation.

The following example is a modified version of the "Attribute" template
for the DDL transformation that sets the "unique" property and creates
the required Operation.

We hope this helps.  If you have any further questions, please feel free
to ask.


=== START TEMPLATE ===

$isUnique = %attTag:"Unique"%
$datatype=%CONVERT_TYPE(genOptDefaultDatabase,attType)%

Column
{
  %TRANSFORM_CURRENT("type", "stereotype", "collection", "constant",
"containment", "ordered", "static", "volatile")%
  type=%qt%$datatype%qt%
%if $isUnique == "TRUE"%
  unique
%endIf%
}

%if $isUnique == "TRUE"%
Operation
{
  name=%qt%UQ_%className%_%attName%%qt%
  stereotype=%qt%unique%qt%
  
  Parameter
  {
    name=%qt%%attName%%qt%
    type=%qt%$datatype%qt%
  }
}
%endIf%

=== END TEMPLATE ===



----------------------------------------------------


Also use the search button, find by message or header and go for posts dating back to more than a year. use mda or  unique or transformation, not null as words to look for.

Sparx is right now changeing the nullable foreign key behaviour of the DDL tool, this might be of interest to you. In the physical model, after transformation took place, the multiplicity of the association between table classes let DDL tool decide, what fk is nullable and what is not.

let me know if you need more to get around your issue
Peter

7

General Board / Re: MDA - assign columns to operations ?

« on: May 04, 2010, 09:49:08 pm »

The parameter element does the trick

8

General Board / Re: MDA - assign columns to operations ?

« on: April 23, 2010, 02:20:59 am »

Try this, not that I am an expert, but I have seen that before.

Greetings

Operation
 {        
        name=%qt%IDX_%CONVERT_NAME(className, "Pascal Case","Camel Case")%Id%qt%
        stereotype=%qt%index%qt%
Parameter
  {
    name="Column1"
    type="Text"
  }

 }

9

General Board / Re: PIM common data types

« on: November 13, 2010, 12:53:08 am »

you are using a new transformation type or a set of transformation types or you are working on existing transformation types (DDL). In the transformation you will probably map the PIM datatype into a PSM datatype. you could use text or string or largeString as a PIM type and transform into varchar() or NVARCHAR2() in the attribute template. Use a tag on the PIM attribute (eg. size) and read the tag value in the attribute template to make a varchar() a varchar(50), varchar(200), varchar(max), clob, whatever. You could even default to varchar(50) if no size tag is given on the PIM attribute.

like->
%if attType == "String"%

%if $sizeTag == ""%
$datatype="NVARCHAR2("+"50"+")"
%else%
$datatype="NVARCHAR2("+$sizeTag+")"
%endIf%
 
%elseIf attType == "LargeString"%
  $datatype = "CLOB"

this code is in the attribute template and the name and type of the creating PSM attribute is set from the evaluated type like

name=%qt%$fullattrname%qt%
type=%qt%$datatype%qt%
%if $isNotNull == "TRUE"%
  NotNull
%endIf%

NotNull is also derived from a tag :-)

cheers
peter

10

General Board / Re: MDA transformation for DDL has default FK NotN

« on: May 04, 2010, 09:37:35 pm »

This was changed and fixed and changed and fixed, as of 8.0, it is very stable and useful imho

11

General Board / Re: MDA transformation for DDL has default FK NotN

« on: November 11, 2008, 07:31:41 pm »

Just a short update:
I also posted to the support and was given a short feedback. Someone is looking for a fix or whatever. I'm not at all sure if the fix will be based on multiplicities of the association or if the FK in the transformation can be  set NotNull with the default changed. I have no idea when the fix will be available.

If someone wants to give some input (Midnight seems to be kind of a reference) please go ahead.

Greetings
Peter

12

General Board / Re: MDA transformation for DDL has default FK NotN

« on: October 29, 2008, 12:21:41 am »

The [0..1] multiplicity on the association would be a fine thing, the Code Engineering DDL would need changes for that to create the correct DDL.
That said, what would the Code Engineering DDL thing (is it a tool?) do with foreign key attribute set to NotNull and source side of the association having multiplicity of [0..1]  

It would have to be documentet somehow, after all

13

General Board / MDA transformation for DDL has default FK NotNull

« on: October 28, 2008, 06:34:14 pm »

Hello
not sure if I picked the right forum, please give me some advice if not.

I'm using MDA transformations to create a Data Model (PSM) out of a Plattform Independant Model (PIM).
Until build 833 an association between two classes in the PIM resulted in a nullable Foreign Key in the PSM, with 833 the default changed to NotNull.
I'm not fully documented on the change, how to influence the default or so, but I think this will brake models that are fine before 833!
The change was after all requested by me, as of my understanding, we had some communication problems after all.

I need a way to tag or whatever the PIM, so that the PSM (Data Model) will be using NotNull FK or Nullable FK, but the decision is done in the PIM.

Does anybody use the MDA style DDL transformations after all?

Step 1:
I would suggest that the transformation, where one defines the foreign key, is the place where the NotNull token is used on the source attribute to "mark" for NotNull foreign key. The foreign key should default to Null, if no NotNull is used here (this is in the transformation from PIM to PSM).

An option would be a defined tag on the association (not my favorite) to set Null or NotNull.

Step 2: is to invoke the Code Engineering -> Generate DDL that does create the DDL. This Part works fine in 833, so it creates Null or NotNull FK based on Nullability of FK Attribute.

Hope this is clear somehow, please let me know if not.

Check your PIM if it will stand the upgrade to 833 after the default changed from Null FK to NotNull FK ! [smiley=thumbdown.gif]

Greetings
Peter

14

General Board / Re: Working offline with TFS version control

« on: October 29, 2008, 10:33:46 pm »

Hello,

you may want to have a look at the Team Explorer, the client for TFS w/o using a real VisualStudio. There are Command Line utilities (tf.exe" checkout ..\theFileYouWantToCheckOut.eap /login:domain\%1,%2) that are maybe working w/o Team Explorer,

or wait for the upcomming PowerTools for TFS with Explorer integration (like TortoiseSVN)

Greetings
Peter

15

Bugs and Issues / Re: Build 855 -> Database Engineering -> DDL Tran.

« on: November 11, 2010, 01:45:47 am »

I submitted this to registered support and hope to get an answer sooner or later :-)