Re: Convention for case of SQL objects

2005-02-15 Thread Brian McCallister
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 fo

Re: Fwd: Convention for case of SQL objects

2005-02-15 Thread Niclas Hedhman
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

RE: Convention for case of SQL objects

2005-02-15 Thread erik
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 ca

Re: Meeting 11-Feb-2005

2005-02-15 Thread Michael Bouschen
Hi Michelle, My notes say that we decided ultimately to leave Person as concrete and to map all the classes in that hierarchy to a Person table. yes, this is what I recall, too. - Person is concrete - Employee is abstract - FullTimeEmployee and PartTimeEmployee are both concrete All of them are ma

Assertion numbers in renumbered JDO spec chapters

2005-02-15 Thread Michael Bouschen
Hi Craig, hi Michelle, some chapters of the JDO spec are renumbered from 1.0 to 2.0: ChapterJDO 1.0 JDO 2.0 Extent15 19 JDO Reference Enhancer20 21 Interface StateManager21 22 JDOPermission 22

Re: Assertion numbers in renumbered JDO spec chapters

2005-02-15 Thread Michelle Caisse
Yes, that does need to be done. I can do that when I have my turn at the spreadsheet. -- Michelle Michael Bouschen wrote: Hi Craig, hi Michelle, some chapters of the JDO spec are renumbered from 1.0 to 2.0: ChapterJDO 1.0 JDO 2.0 Extent15 19

Re: Assertion numbers in renumbered JDO spec chapters

2005-02-15 Thread Michael Bouschen
Hi Michelle, I thought about this again and meanwhile I'm not sure whether we should do the renumbering of the assertions. It is a lot of work changing the spreadsheet and the corresponding TCK test classes. But what concerns me more is that all the TCK test cases we have today are valid JDO 1

Re: Apache development project

2005-02-15 Thread Craig Russell
Javadogs, So when I tried to subscribe [EMAIL PROTECTED] to jdo-dev@db.apache.org, I realized I don't know how to do it. The subscribe message takes the "from" email address. And I don't know how to fake this. Can anyone help? Craig On Feb 11, 2005, at 1:10 PM, Geoff hendrey wrote: Put us all o

Re: Fwd: Convention for case of SQL objects

2005-02-15 Thread Robin M. Roos
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 wrot

Re: Assertion numbers in renumbered JDO spec chapters

2005-02-15 Thread Michelle Caisse
I'm fine with either approach. I think you're right about the problem with the JDO1 spec, so let's change the numbers back in the 2.0 spec. -- Michelle Michael Bouschen wrote: Hi Michelle, I thought about this again and meanwhile I'm not sure whether we should do the renumbering of the assertio