When I create an attribute or domain in LM of type (say) Integer, then generate PM the type becomes Number(,). The Data Type Conversion dialog (LM->Ora9i) shows Integer should convert to Number(x,y) Param1 = 10, Param2 = 0. So I expect to get Number(10,0) in PM.
Also if I create a default rule in LM with SQL content, the conversion inserts SQL comment “–” in front of the SQL content. This then has to be edited in PM to remove the “–”.
How can I overcome these issues?
Data type parameters during conversion
Yes, you’re right. This is a bug. It was already reported and is registered under CR # 39 467. We will fix it.
Also if I create a default rule in LM with SQL content, the conversion inserts SQL comment “–” in front of the SQL content.
It is a corrrect behaviour. SQL code is commented (for LER to PER conversion and PER to PER conversion as well). The reason for this behaviour is that the LER model can be converted to PER model of any database (Oracle, SQL Server, PostgreSQL…). The SQL code can contain items that are database dependent. (In other words, there is not an SQL code that would be the same for all databases.) So, user has to go through the code, check it out and make necessary modifications.
We can imagine, this is annoying when you know you will convert your Logical model to Oracle db while writing the code and regardless have to edit it after the conversion.
So, we can suggest you the following solution - enhancement in some of next TDM3 releases: you will be allowed to select whether you like to comment the code or not. (It would be applied to all SQL codes.)
Is this suggestion acceptable for you? Please let us know.
If so, I’ll create a new CR for our developers.
Vladka + TDM Team
I thought this was probably why the SQL was commented.
Yes - it would be useful to be able to specify for each conversion. Maybe we could set a default of "Comment or “Not comment”, then override that for each conversion.
Thanks for your response.
I’m pleased to inform you that we will make a system where you will be able to define the settings (even for individual items of the code) and save the settings. Then you will be able to select the one you need for particular conversion.
CR # 43 682.
Thanks for your great co-operation!
Vladka + TDM Team