Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - bilon

Pages: 1 [2] 3 4
In this case, it isn't definitely without issues. The issue is, that after setting datatype to "char" in step 1, it is displayed as "varchar" in step 2. They should be same.

We need to create parametrized script and enable users to set parameters interactively. My idea is to open add-in window from the script, which would enable to change the parameters, and then continue with the script or to call another script which would do the rest of work. Is it possible to do something like this or is it absolute nonsense?

What do you mean with "worked with no issues"? Does it mean, that the output looked like this:
1: TABLE_NAME char
2: TABLE_NAME char

The reason why tab.Attributes.Refresh is commented, is, that tested it but it didn't work, so I commented it. Even tab.Refresh doesn't work!

As you can see, Refresh is already there. But commented, because it doesn't help.

I have simple script changing single property of elements attribute and subsequently iterating through elements attributes to display the new value. But the old value is displayed. Here is the script:

Sub Main
   Dim tab AS EA.Element
   Dim col AS EA.Attribute
   For Each tab In Repository.GetTreeSelectedElements
      For Each col In tab.Attributes
         If col.Name = "TABLE_NAME" Then
            Select Case col.Type 
               Case "varchar"
               col.Type = "char"
               Session.Output "1: " & col.Name & " " &  col.Type
               '1: TABLE_NAME char
            Case Else   
            End Select
         End If      
      For Each col In tab.Attributes
         If col.Name = "TABLE_NAME" Then
            Session.Output "2: " & col.Name & " " &  col.Type
            '2: TABLE_NAME varchar
         End If
End Sub

The new value is correctly saved to model, so why it is not displayed in the script?

General Board / Columnstore indexes for Sql Server tables
« on: January 02, 2018, 09:52:28 pm »

when modelling index for Sql Server table, I can't see any option for columnstore indexes. Is there any way how to accomplish this?



we currently face the same error as described in this topic,5480.msg125188/topicseen.html#msg125188
It is marked as solved, but I can't see there any solution. Is anybody able to help me? After adding new element to the collection and setting it's properties, subsequent update of this element ends up with mentioned error. Interesting is, that when not setting StereotypeEx property, it works fine. It works fine too (even when setting StereotypeEx property) when used against eap file. But in MySQL repository it ends up with the error.


In my case, the elements are relatively simple, so I can't see any problems in duplication. Anyway, if duplication is possible through user interface, why it is not possible in scripting?

Same as the original.

Looks to be pretty hard work  :(

Any idea how duplicate element from script? I need to do in script the same as do the browser functions "Copy element to clipboard" and "Paste element from clipboard".

Is there anybody capable to help me?

MDA transformations are quite new topic for me. After reading some kind of "documentation", I must say I have no idea what I should manipulate. There's some DDL Transformation, but this (according the documentation) is the process of transforming logical model into physical model. My problem is, that I have valid physical (data) model for Sql Server, but EA generates bad DDL script from it. Anyway, manipulating MDA transformations looks like pretty low level activity - it is in no way "simple workaround" of core product error.

General Board / Sql Server Datetime2 datatype length poorly generated in DDL
« on: September 15, 2017, 10:34:50 pm »
When setting DATETIME2 length to non-zero value, it's ok. For zero length EA generates DATETIME without length, which defaults to 7 in Sql Server. Does anybody know some workaround?

Pages: 1 [2] 3 4