-
Uncategorized
-
- Join this Course to access resources
- Join this Course to access resources
-
- Join this Course to access resources
- Join this Course to access resources
-
- Join this Course to access resources
- Join this Course to access resources
- Join this Course to access resources
-
- Join this Course to access resources
- Join this Course to access resources
-
- Join this Course to access resources
- Join this Course to access resources
-
- Join this Course to access resources
- Join this Course to access resources
-
- Join this Course to access resources
- Join this Course to access resources
-
- Join this Course to access resources
- Join this Course to access resources
-
- Join this Course to access resources
- Join this Course to access resources
-
- Join this Course to access resources
- Join this Course to access resources
-
- Join this Course to access resources
- Join this Course to access resources
-
- Join this Course to access resources
- Join this Course to access resources
-
- Join this Course to access resources
- Join this Course to access resources
-
- Join this Course to access resources
- Join this Course to access resources
-
Naming Conventions
Hackolade Studio includes the ability to maintain both a ‘business name’ and a ‘technical name’ for objects (containers, entities, and attributes.) To facilitate the maintenance of these 2 names, it is possible to keep them synchronized and transformed based on a set of user-driven parameters, and optionally based on a conversion file maintained outside of the application. Name conversion can go both directions: Business-to-Technical, or Technical-to-Business. Furthermore, when performing reverse-engineering, it is assumed that the database instance contains technical names, to be transformed in business names.
Rating
0
0
There are no comments for now.
Join this Course
to be the first to leave a comment.
Additional Resources
Join this Course to access resources