Access lower/upper bound/multiplicity of param

[b1256]

Hello,

How can I access LowerBound, UpperBound or Multiplicity of a parameter from code generation template?

[Eve]

I don't think you can.

[qwerty]

Wasn't it possible to call an add-in from inside the code gen (haven't iused that for a long time).

q.

[Eve]

Yes, you can call an add-in (search for EXEC_ADD_IN,) but from what I can see it won't help you.

[Geert Bellekens]

Even if those fields are not exposed in the API object you can still get them from the database using Repository.SQLQuery()

Geert

[smither]

I see why using an add-in might be difficult!  This is another case of where the API does not support all the properties of the model - there is no API method or property to obtain the Multiplicity or the control of orderedness and uniqueness of a parameter.  In the database its squirreled away in the t_xref table (Qwerty .. it's time to document this beast, please), and can be got through an SQL query:

Code: [Select]

select x.Description
from t_xref as x, t_object as o, t_operation as op, t_operationparams as p
where o.Name = "<className>"
and op.Name = "<operationName"
and p.Name = "<parameterName>"
and x.Type = "parameter property"
and op.Object_ID = o.Object_ID
and p.OperationID = op.OperationID
and x.Client = p.ea_guid
which returns a string of the form:

Code: [Select]

@PROP=@NAME=lower@ENDNAME;@TYPE=Integer@ENDTYPE;@VALU=77@ENDVALU;@PRMT=@ENDPRMT;@ENDPROP;@PROP=@NAME=upper@ENDNAME;@TYPE=UnlimitedNatural@ENDTYPE;@VALU=99@ENDVALU;@PRMT=@ENDPRMT;@ENDPROP;@PROP=@NAME=isOrdered@ENDNAME;@TYPE=Boolean@ENDTYPE;@VALU=1@ENDVALU;@PRMT=@ENDPRMT;@ENDPROP;@PROP=@NAME=isUnique@ENDNAME;@TYPE=Boolean@ENDTYPE;@VALU=0@ENDVALU;@PRMT=@ENDPRMT;@ENDPROP;
Then all you need to do is parse it!  (Or you could request that Sparx extend the api and the field substitution macros to cover this.)

[qwerty]

Qwerty .. it's time to document this beast, please

It's a beast, you tell it. For that reason I did not dig too deep into t_xref. I still hope for a re-design of the database in some future EA version. But that will likely not be soon. In the meantime I'll take that and gather some more information about t_xref to put it into the book.

q.

[b1256]

Thank you all for your good suggestions and discussion!