You’re offline. This is a read only version of the page.
65
I'm curious what prefix naming conventions people use. I am yet to have a go to method but have some ideas, I am curious what you guys use! Feedback on mine or examples of what you do would be appreciated!
I tend to prefer pascal case and then add underscores for further descriptions on things like data-types and relationships.
Entities: I use pascal case
- e.g. Address, Employee, SiteInspection
Primary Key: Use entity name with Key as suffix
- e.g. AddressKey, EmployeeKey, SiteInspectionKey (initially I was going to use ID as suffix but dataverse doesn't allow this because it auto generates a column with ID as suffix)
Foreign Key: I use FK as prefix and I usually try to find a good description of the relationship but if not I will just put it in the form "FK_child_parent"
- e.g. FK_SiteVisitor (relationship between Employee and SiteInspection)
- e.g. FK_Employee_Address (relationship between Employee (child) and Address (parent), this would be an example of a relationship where I couldn't find a useful/better description)
Columns with "special" data-types: I have been experimenting with adding prefixes and especially feedback here would be appreciated if you think this is a good idea or not.
- e.g. Deadline_datetime (for attributes with dates)
- e.g. EmployeeRole_choice (for attributes with choice)
- e.g. Active (for attributes with boolean value, currently don't have modified naming convention)
I would be interested to see what other people do or if you have suggestions on mine!
Thanks,
Jason
Share
Report
All responses (
Answers (
