1
 Follower
1
 Like

[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.

Integration
Not right now

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. 




Created on 19 Sep 2015
Comments (1)
Changed the status to
Not right now


Hi,


Sorry for the late reply, but we are not planning on delivering this in the near future.


Although this totally makes sense, with the upcoming new features that we have in mind we currently don't have plans to tackle this in the near future.


Nonetheless, thank you very much for your idea and keep it coming.

If you believe we missed some context that would change our perception about it, please give us more details about why you would need this and for what is the use case.


 Thanks!

views
201
Followers
1