Watch, Follow, &
Connect with Us

For forums, blogs and more please visit our
Developer Tools Community.

Welcome, Guest
Guest Settings

Thread: View Naming

This question is not answered. Helpful answers available: 2. Correct answers available: 1.

Permlink Replies: 1 - Last Post: Jan 28, 2015 5:26 PM Last Post By: Jason Hahn Threads: [ Previous | Next ]
Andrew Thompson

Posts: 1
Registered: 12/14/14
View Naming  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jan 28, 2015 3:29 AM
When creating a view in the LDM ER studio correctly use the logical names for column and fields. However, when generating the physical it does not use the naming template and creates the view using the logical names which subsequently fails to validate at the physical level. I have tried creating the view in the physical model and merging back to the logical but this create a logical view with the physical names and again fails to validate.

A possible work around is to create the view with all the alias as per the naming template but this is an overly manual process and subject to error. Also, when applying the alias on the column tab, it is not replicated correctly in the where tab.

I am using a naming template agreed with the business but nothing looks out of the ordinary (Camel Case, Standard Abbreviation etc.)

Does anyone know if I am doing something stupid, whether this is an error or a 'design feature'...
Jason Hahn

Posts: 10
Registered: 10/12/08
Re: View Naming  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jan 28, 2015 5:26 PM   in response to: Andrew Thompson in response to: Andrew Thompson
Hi Andrew,

I'd suggest applying the naming standards template to the logical model to update the physical names in the LDM. (Go to Model > Naming Standards Utility, then make sure the Source is set to Logical and Target is set to Physical before selecting your objects and running the translation.)

In my tests, when I have the physical names already applied in the logical model, and then generate the physical model, the view is updated with the physical names and validates correctly. Unfortunately, comparing and merging between the logical and physical won't work as long as the two models use different names.


Check out Embarcadero's new community site, including its Data Modeling subforum:
Helpful Answer (5 pts)
Correct Answer (10 pts)

Server Response from: ETNAJIVE02