Anil,

Good question... I think as long as the name implies it is a view- entity and somewhat describes the intent (often including elements of the member-entity names), then it is fine.

-David


On Feb 5, 2007, at 10:43 AM, Anil Patel wrote:

Hi,
I am little confused over naming a View Entity. Few examples from code base
are

"WorkEffortAndPartyAssign" A view on WorkEffort and
WorkEffortPartyAssignment, The pattern here is have AND between names of
Entity comprising the view.
"WorkEffortPartyAssignView" The pattern here is Names of entities followed
by VIEW keyword to identify that its a view.
"ExampleStatusDetail" This view has Detail Suffix.

May be I am thinking too much here, but for me naming takes good amount of time, just so the code gets easily accepted. I'll appreciate input from community for putting together some high level guidelines on Naming a view, Specially most common simple views that are build on top of two or three
entities.

Thanks and Regards
Anil Patel

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to