Re: JDO API compability with JDK 1.3

2005-07-21 Thread Daniel John Debrunner
From: Michael Bouschen [EMAIL PROTECTED] I have a question what kind of JDK 1.3 compatibility do we want to support? I see that JDO plans to support JDK 1.3 from the wiki, but I was wondering why? Given the end of service dates for the various 1.3 VMs I was thinking that Derby 10.1 could be

Re: JDO API compability with JDK 1.3

2005-07-21 Thread Craig Russell
Hi Dan,On Jul 21, 2005, at 2:18 AM, Daniel John Debrunner wrote:From: Michael Bouschen [EMAIL PROTECTED] I have a question what kind of JDK 1.3 compatibility do we want tosupport?  I see that JDO plans to support JDK 1.3 from the wiki, but I waswondering why? Given the end of service dates for

Re: Binding a char to PreparedStatement

2005-07-21 Thread Craig Russell
Hi Erik,On Jul 21, 2005, at 2:10 AM, [EMAIL PROTECTED] wrote:Ok. I thought that you would agree that this is a bug in JPOX, since the "obvious default" for a char column is CHAR. It is not that obvious when you have to support a wide range of databases and data types. The most obvious choice to

Re: Binding a char to PreparedStatement

2005-07-21 Thread erik
I'm not aware of any database that doesn't support CHAR column type. And I think that having a default of jdbc-type = CHAR for a char field is very reasonable. If I put this into the specification, I assume you would be ok with it? I would be very ok, if you show me how to store a char

JDO TCK Conference Call Friday, Jul 22, 9 am PST

2005-07-21 Thread Michelle Caisse
Hi, We will have our regular meeting Friday, July 22 at 9 am PST to discuss JDO TCK issues and status. Dial-in numbers are: 866 230-6968 294-0479# International: +1 865 544-7856 Agenda: Metadata Tests (Michelle, Michael) Character truncation issue status (Michael, Craig) JPOX

Re: Binding a char to PreparedStatement

2005-07-21 Thread Craig Russell
Hi Erik,On Jul 21, 2005, at 2:10 AM, [EMAIL PROTECTED] wrote:See inlineErik Bengtson-Original Message-From: Craig Russell [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 21, 2005 12:26 AMTo: jdo-dev@db.apache.orgSubject: Re: Binding a char to PreparedStatement I was thinking that most of

Re: svn commit: r220215 - in /incubator/jdo/trunk/tck20/test: orm/applicationidentity/org/apache/jdo/tck/pc/company/ orm/datastoreidentity/org/apache/jdo/tck/pc/company/ sql/derby/applicationidentity/

2005-07-21 Thread Michelle Caisse
This is simply an attempt to use the name attribute of the foreign-key element in the metadata, as specified on the XML Metadata Test Coverage wiki page http://wiki.apache.org/jdo/Chapter18TestComponents. It's probably not very useful right now because we are not testing schema generation.

Re: svn commit: r220215 - in /incubator/jdo/trunk/tck20/test: orm/applicationidentity/org/apache/jdo/tck/pc/company/ orm/datastoreidentity/org/apache/jdo/tck/pc/company/ sql/derby/applicationidentity/

2005-07-21 Thread Craig Russell
Hi Michelle,It makes sense now. I was confused because it doesn't actually test anything yet, except that the foreign-key element is parsed by the xml parser.We will discuss it tomorrow.Thanks,CraigOn Jul 21, 2005, at 9:13 PM, Michelle Caisse wrote:This is simply an attempt to use the name