From: esquel@sommarskog.se   
      
   gargoyle60 (gargoyle60@example.invalid) writes:   
   > I was trained in SQL years ago and was encouraged to use lower-case   
   > letters with words separated for emphasis using the underscore   
   > character, for example:   
   >      customer_num, employee_id, invoice_line, transaction_code   
   >   
   > I've stuck with this approach ever since, but now that I make use of   
   > oo programming the general standard is to name oo instance variables   
   > without underscores and capitalising all words except the first for   
   > emphasis, such as:   
   >      customerNum, employeeId, invoiceLine, transactionCode   
   >   
   > However, bridging the gap between relational databases and oo   
   > programming means that when binding table column names to object   
   > variable names, I really need to pick one or the other (you may   
   > disagree but that's my aim).   
   >   
   > So, when it comes to naming columns, what are most of you using?   
      
   All lowercase, using underscore only exceptionally. (When no underscore   
   would make the name to confusing.)   
      
   Look at it this way: if you use different conventions for columns   
   and class members, you can easily tell them apart.   
      
      
   --   
   Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se   
      
   Links for SQL Server Books Online:   
   SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx   
   SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx   
   SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)