C
Chris Fulstow
Hi,
What are people's thoughts on naming convention for data access
components?
I'm building two classes that will be used by an ObjectDataSource for
data binding:
1. Data entity (encapsulates a single record, e.g. Employee)
2. Utility class (performs employee ADO.NET database operations)
I'm fairly settled on "Employee", but can't decide what to call the
utility class?
- EmployeeDB
- EmployeeFactory
- EmployeeUtility
- EmployeeData
- Employees
Any thoughts?
Chris
What are people's thoughts on naming convention for data access
components?
I'm building two classes that will be used by an ObjectDataSource for
data binding:
1. Data entity (encapsulates a single record, e.g. Employee)
2. Utility class (performs employee ADO.NET database operations)
I'm fairly settled on "Employee", but can't decide what to call the
utility class?
- EmployeeDB
- EmployeeFactory
- EmployeeUtility
- EmployeeData
- Employees
Any thoughts?
Chris