When adding a new Telerik OpenAccess Domain Model (version 2010.3.1125.1), I take the following steps:
- Populate from database
- Using an Oracle backend (ODP for Oracle Client 11.1.0.6.21)
- Select the desired table "CAMPAIGN_LIST"
- Under define classes I choose:
- Case: Pascal
- Remove underscores
- Interpret underscore as word delimiter
I would assume the outputted class would be “CampaignList”. However, the class that gets created is “CAMPAIGNLIST”. The same happens for properties and fields.
How do I get the output to be “CampaignList”?
3 Answers, 1 is accepted
Our naming generation mechanism treats the capital letters as start of new words. So for example if you have My_OrderDetails and you prepare the same setup as yours what would you expect to get? MyOrderDetails or Myorderdetails? We believe that the second is more correct. Treating capital letters as start of words makes it possible for us to recognize different words that are not separated in any way. You will have to agree that it would be near to impossible to distinguish the different words in myorderdetails without depending on the capital letters. Perhaps if we make an option that disables this feature and only depends on predefined delimiters (like underscore) maybe that will work for you?
We look forward to your opinion on the matter.
Petar
the Telerik team
Rank 2
Currently, we are unable to use OpenAccess ORM because of this naming issue. An option to use the predefined delimiter as the word separator is exactly what we need. Please let me know if this enhancement ever gets into the OpenAccess ORM product.
Also, I have a couple other minor enhancement requests for the OpenAccess ORM. Should they be posted to the feature request forum?
If you have some already defined request it will be best if you submit a feature request.
As for the enchantment you suggested - yes it will get in the product however I am not able to provide you with a time frame at this point.
Petar
the Telerik team