Convention for case of SQL objects
Hi, all, What capitalization convention would you like to see used for names of tables, views, columns, indexes and constraints in SQL commands used in the TCK? Choices are lower_case, UPPER_CASE, Initial_upper_case or CamelCase. Practice seems to vary from author to author. -- Michelle
RE: Convention for case of SQL objects
I like UPPER_CASE... >-Original Message- >From: Michelle Caisse [mailto:[EMAIL PROTECTED] >Sent: Monday, February 14, 2005 3:41 PM >To: jdo-dev@db.apache.org >Subject: Convention for case of SQL objects > > >Hi, all, > >What capitalization convention would you like to see used for names of >tables, views, columns, indexes and constraints in SQL >commands used in >the TCK? Choices are lower_case, UPPER_CASE, Initial_upper_case or >CamelCase. Practice seems to vary from author to author. > >-- Michelle >
Fwd: Convention for case of SQL objects
Please reply to jdo-dev alias as well as jdo-experts alias. This is not a super important issue but it's very timely. Thanks, Craig Begin forwarded message: From: Michelle Caisse <[EMAIL PROTECTED]> Date: February 14, 2005 3:41:28 PM PST To: jdo-dev@db.apache.org Subject: Convention for case of SQL objects Reply-To: jdo-dev@db.apache.org Hi, all, What capitalization convention would you like to see used for names of tables, views, columns, indexes and constraints in SQL commands used in the TCK? Choices are lower_case, UPPER_CASE, Initial_upper_case or CamelCase. Practice seems to vary from author to author. -- Michelle Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! smime.p7s Description: S/MIME cryptographic signature
Re: Convention for case of SQL objects
First choice is UPPER_CASE second choice is lower_case -Brian On Feb 14, 2005, at 6:42 PM, Matthew T. Adams wrote: I like UPPER_CASE... -Original Message- From: Michelle Caisse [mailto:[EMAIL PROTECTED] Sent: Monday, February 14, 2005 3:41 PM To: jdo-dev@db.apache.org Subject: Convention for case of SQL objects Hi, all, What capitalization convention would you like to see used for names of tables, views, columns, indexes and constraints in SQL commands used in the TCK? Choices are lower_case, UPPER_CASE, Initial_upper_case or CamelCase. Practice seems to vary from author to author. -- Michelle
RE: Convention for case of SQL objects
Since this is intended to test the implementation, why not use all of them? Erik Bengtson -Original Message- From: Michelle Caisse [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 15, 2005 12:41 AM To: jdo-dev@db.apache.org Subject: Convention for case of SQL objects Hi, all, What capitalization convention would you like to see used for names of tables, views, columns, indexes and constraints in SQL commands used in the TCK? Choices are lower_case, UPPER_CASE, Initial_upper_case or CamelCase. Practice seems to vary from author to author. -- Michelle
Re: Fwd: Convention for case of SQL objects
On Tuesday 15 February 2005 07:49, Craig Russell wrote: > Please reply to jdo-dev alias as well as jdo-experts alias. > > This is not a super important issue but it's very timely. :o) IMHO, I think the UPPERCASE that is still preferred by many DB admins are a relic from COBOL days, and that the CamelCase is both easier to read. But since Tables maps roughly with classes and columns roughly to members, wouldn't it make sense to preserve case at all times when automated and 'use' same case when manually mapped? I also think this is a non-issue in that if there is already something in place, then use it. Don't spend time on a change. Cheers Niclas
Re: Fwd: Convention for case of SQL objects
The conventions which I'm used to here in London are: table names: capitals with _ separator column names: lowercase with _ separator e.g. EMPLOYEE_PAYROLL.employee_id On Mon Feb 14 20:37:40 PST 2005, Niclas Hedhman <[EMAIL PROTECTED]> wrote: On Tuesday 15 February 2005 07:49, Craig Russell wrote: Please reply to jdo-dev alias as well as jdo-experts alias. This is not a super important issue but it's very timely. :o) IMHO, I think the UPPERCASE that is still preferred by many DB admins are a relic from COBOL days, and that the CamelCase is both easier to read. But since Tables maps roughly with classes and columns roughly to members, wouldn't it make sense to preserve case at all times when automated and 'use' same case when manually mapped? I also think this is a non-issue in that if there is already something in place, then use it. Don't spend time on a change. Cheers Niclas
