Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Date: Fri, 14 Jan 2005 11:48:45 -0800
From: Craig Russell <Craig.Russell@Sun.COM>
Subject: Re: Database (was: RE: Questions)
In-reply-to: <001a01c4fa70$f7c94360$0263a8c0@DELLZILLA>
To: jdo-dev@db.apache.org
Message-id: <4CEB9CB2-6665-11D9-A87A-000A95BCB4AE@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: QUOTED-PRINTABLE
References: <001a01c4fa70$f7c94360$0263a8c0@DELLZILLA>

We are going to build a ddl generator program as part of the tck, but=
 I=20
agree with Matthew that we might not have time to pull it off. So we=
=20
need to define the various test cases, object model, mapping, databas=
e=20
schema, and test data. We will have to hand construct the database=
=20
schema to begin with, and we should discuss what schema it should be.

Considering that we're an Apache Database project, the natural choice=
=20
would be Derby, but considering that we might have time for only one,=
=20
we might choose "SQL92" since deltas from the standard would probably=
=20
be the JDO implementation's responsibility.

Craig

On Jan 14, 2005, at 11:40 AM, Matthew T. Adams wrote:

> The problem with being able to run against any database is the
> difference in SQL dialects.  While I would like the ideal, I don't =
know
> that we have the resources to actually pull it off.  Remember, time=
 is
> of the essence here; the specification is nearly complete, but can'=
t be
> officially final until the RI & TCK are done.
>
> --matthew
>
>> -----Original Message-----
>> From: Brian McCallister [mailto:brianm@apache.org]
>> Sent: Friday, January 14, 2005 11:17 AM
>> To: jdo-dev@db.apache.org
>> Subject: Re: Questions
>>
>>
>> I would suggest Derby or in-memory HSQLDB for system tests =3D) Th=
at
>> said, i would definitely recommend making it really easy to run te=
sts
>> against any supported database. Ideally a one line config change i=
n
>> build process, or override via an ant -D switch.
>>
>> -Brian
>>
>> On Jan 14, 2005, at 1:55 PM, Matthew T. Adams wrote:
>>
>>> Hi all,
>>> =A0
>>> A few questions:
>>> =A0
>>> * When will someone be uploading the next update to the private J=
DO
>>> area?
>>> * Is there a preferred IDE that we should use in order to lessen =
the
>>> impedance while getting started?
>>> * Have we selected a particular database to test against?
>>> =A0
>>> --matthew
>>> =A0
>>> Matthew T. Adams
>>> Corporate Technical Advisor & Senior Consultant
>>> Mobile:=A0 +1 253 732 1051
>>> Phone:=A0 +1 206 331 3833
>>> Fax:=A0 +1 360 937 9616
>>> matthew.adams@xcalia.com
>>> P.O. Box 24163
>>> Federal Way, WA=A0 98093
>>> www.xcalia.com
>>> =A0
>>> <image.tiff>=A0
>>> Xcalia helps businesses address the challenge of Enterprise
>>> Information Access in=A0a heterogeneous environment.=A0 We provid=
e
>>> products and services that facilitate the two-way exchange of
>>> information between individuals, mission-critical applications, a=
nd
>>> databases.=A0 Our customers enjoy improved performance, reduced
>>> operating and development costs, faster time to market, and
>>> rejuvenated legacy systems.
>>> =A0
>>
>
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jd=
o
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!