Comments on: Naming Conventions and the Underscore http://blog.todmeansfox.com/2009/06/15/naming-conventions-underscore/ Supporting decisions through sound data management Tue, 23 Aug 2011 03:10:04 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: doug k http://blog.todmeansfox.com/2009/06/15/naming-conventions-underscore/comment-page-1/#comment-14486 doug k Fri, 14 Aug 2009 12:56:10 +0000 http://blog.todmeansfox.com/?p=777#comment-14486 i could not agree more- VIN really brought it home- now if i could only get everyone else in the office to read this article.... i could not agree more- VIN really brought it home- now if i could only get everyone else in the office to read this article….

]]> By: Tod McKenna http://blog.todmeansfox.com/2009/06/15/naming-conventions-underscore/comment-page-1/#comment-13821 Tod McKenna Tue, 23 Jun 2009 05:08:33 +0000 http://blog.todmeansfox.com/?p=777#comment-13821 Of course, you could always just adopt the least common denominator and avoid CamelCase entirely. I like CamelCase very much, so it would take a lot of arm twisting for me to abandon it to support a database version (or property sheet!). Of course, you could always just adopt the least common denominator and avoid CamelCase entirely. I like CamelCase very much, so it would take a lot of arm twisting for me to abandon it to support a database version (or property sheet!).

]]> By: Tod McKenna http://blog.todmeansfox.com/2009/06/15/naming-conventions-underscore/comment-page-1/#comment-13820 Tod McKenna Tue, 23 Jun 2009 05:04:15 +0000 http://blog.todmeansfox.com/?p=777#comment-13820 Ideally, you would adopt a convention that was consistent across the entire development environment. When that cannot be done, or if it is not practical, then my advice would be to simply confine your naming conventions to the environment. C# remembers case, so all objects and variables created in C# should use CamelCase. Because the database does not, use the underscore as mentioned above. Therefore, In your C# code, ProductKey = product_key. If you have a good multi-tiered design, many of these problems should disappear or at least be confined to code in that tier. You can also use aliases judiciously to mask (in this example) the database's inability to remember case. Ideally, you would adopt a convention that was consistent across the entire development environment. When that cannot be done, or if it is not practical, then my advice would be to simply confine your naming conventions to the environment. C# remembers case, so all objects and variables created in C# should use CamelCase. Because the database does not, use the underscore as mentioned above. Therefore, In your C# code, ProductKey = product_key. If you have a good multi-tiered design, many of these problems should disappear or at least be confined to code in that tier. You can also use aliases judiciously to mask (in this example) the database’s inability to remember case.

]]> By: John Smith http://blog.todmeansfox.com/2009/06/15/naming-conventions-underscore/comment-page-1/#comment-13818 John Smith Tue, 23 Jun 2009 00:27:34 +0000 http://blog.todmeansfox.com/?p=777#comment-13818 I have a question. Say your backend is Oracle database that does not support case, so you have columns like Product_Key, and your frondend is C#, so you have fields like ProductKey, now how do you map these fields? I mean you may have to modify every places that wizard generate for you. I have a question. Say your backend is Oracle database that does not support case, so you have columns like Product_Key, and your frondend is C#, so you have fields like ProductKey, now how do you map these fields? I mean you may have to modify every places that wizard generate for you.

]]> By: Weekly Link Post 99 « Rhonda Tipton’s WebLog http://blog.todmeansfox.com/2009/06/15/naming-conventions-underscore/comment-page-1/#comment-13805 Weekly Link Post 99 « Rhonda Tipton’s WebLog Sun, 21 Jun 2009 09:32:42 +0000 http://blog.todmeansfox.com/?p=777#comment-13805 [...] Tod McKenna has some good ideas on Naming Conventions and the Underscore. [...] [...] Tod McKenna has some good ideas on Naming Conventions and the Underscore. [...]

]]> By: Eric Wisdahl http://blog.todmeansfox.com/2009/06/15/naming-conventions-underscore/comment-page-1/#comment-13770 Eric Wisdahl Tue, 16 Jun 2009 14:44:14 +0000 http://blog.todmeansfox.com/?p=777#comment-13770 Amen! Too often people do not set the standard for names prior to a project. Just as often, a standard is set, but revolves around technology that is not even being used. (how often have I had to use upper case with underscores because ONE of the systems in the enterprise has this constraint {and will soon be rolled off} ?) Setting the standard and getting sign off prior to beginning is essential. Amen! Too often people do not set the standard for names prior to a project. Just as often, a standard is set, but revolves around technology that is not even being used. (how often have I had to use upper case with underscores because ONE of the systems in the enterprise has this constraint {and will soon be rolled off} ?)

Setting the standard and getting sign off prior to beginning is essential.

]]>