[Integration Studio] When a database is imported, all naming should be converted to camel casing (alias),  in order for the imported database entities to display and use correctly with scaffolding via service studio.

By Robert Chanphakeo on 19 Sep 2015
When a database is imported, all naming should be converted to camel casing (alias),  in order for the imported database entities to display and use correctly with scaffolding via service studio.


Example
Lowercase with an underscore word separator (mysql database standard naming convention)
user_account_role ----> UserAccountRole

Uppercase with an underscore word separator (Oracle database standard naming convention
USER_ACCOUNT_ROLE ---> UserAccountRole


Note: Original table, column naming should be kept in order to avoid issues and for developers own viewing, the original name is to be displayed in the property details, similar to expose REST structure, structure attribute original name property. 



This idea has no comments yet. Be the first to comment!