You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by "Matthew T. Adams" <ma...@xcalia.com> on 2005/01/14 19:55:17 UTC
Questions
Hi all,
A few questions:
* When will someone be uploading the next update to the private JDO
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?
--matthew
Matthew T. Adams
Corporate Technical Advisor & Senior Consultant
Mobile: +1 253 732 1051
Phone: +1 206 331 3833
Fax: +1 360 937 9616
matthew.adams@xcalia.com
P.O. Box 24163
Federal Way, WA 98093
www.xcalia.com <http://www.xcalia.com/>
Xcalia helps businesses address the challenge of Enterprise Information
Access in a heterogeneous environment. We provide products and services
that facilitate the two-way exchange of information between individuals,
mission-critical applications, and databases. Our customers enjoy
improved performance, reduced operating and development costs, faster
time to market, and rejuvenated legacy systems.
Re: Database (was: RE: Questions)
Posted by Craig Russell <Cr...@Sun.COM>.
We are going to build a ddl generator program as part of the tck, but I
agree with Matthew that we might not have time to pull it off. So we
need to define the various test cases, object model, mapping, database
schema, and test data. We will have to hand construct the database
schema to begin with, and we should discuss what schema it should be.
Considering that we're an Apache Database project, the natural choice
would be Derby, but considering that we might have time for only one,
we might choose "SQL92" since deltas from the standard would probably
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 =) That
>> said, i would definitely recommend making it really easy to run tests
>> against any supported database. Ideally a one line config change in
>> build process, or override via an ant -D switch.
>>
>> -Brian
>>
>> On Jan 14, 2005, at 1:55 PM, Matthew T. Adams wrote:
>>
>>> Hi all,
>>>
>>> A few questions:
>>>
>>> * When will someone be uploading the next update to the private JDO
>>> 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?
>>>
>>> --matthew
>>>
>>> Matthew T. Adams
>>> Corporate Technical Advisor & Senior Consultant
>>> Mobile: +1 253 732 1051
>>> Phone: +1 206 331 3833
>>> Fax: +1 360 937 9616
>>> matthew.adams@xcalia.com
>>> P.O. Box 24163
>>> Federal Way, WA 98093
>>> www.xcalia.com
>>>
>>> <image.tiff>
>>> Xcalia helps businesses address the challenge of Enterprise
>>> Information Access in a heterogeneous environment. We provide
>>> products and services that facilitate the two-way exchange of
>>> information between individuals, mission-critical applications, and
>>> databases. Our customers enjoy improved performance, reduced
>>> operating and development costs, faster time to market, and
>>> rejuvenated legacy systems.
>>>
>>
>
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Database (was: RE: Questions)
Posted by Brian McCallister <br...@chariotsolutions.com>.
Even better =)
-Brian
On Jan 14, 2005, at 2:58 PM, Craig Russell wrote:
> Just to clarify, we want to make it as easy as possible for JDO
> vendors to run TCK against all their supported databases. That's why
> we want the ddl generator that can be configured by the test run
> person.
>
> I don't think it makes sense for a compliant JDO implementation to
> only run against a SQL92 database.
>
> Craig
>
> On Jan 14, 2005, at 11:51 AM, Brian McCallister wrote:
>
>> For the TCK, it is probably safe to specify any SQL92 compliant
>> database, and we are just careful about the DDL. For the
>> implementation of JDO it is pointless to only work against one
>> database =)
>>
>> -Brian
>>
>> On Jan 14, 2005, at 2:40 PM, 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 =) That
>>>> said, i would definitely recommend making it really easy to run
>>>> tests
>>>> against any supported database. Ideally a one line config change in
>>>> build process, or override via an ant -D switch.
>>>>
>>>> -Brian
>>>>
>>>> On Jan 14, 2005, at 1:55 PM, Matthew T. Adams wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> A few questions:
>>>>>
>>>>> * When will someone be uploading the next update to the private JDO
>>>>> 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?
>>>>>
>>>>> --matthew
>>>>>
>>>>> Matthew T. Adams
>>>>> Corporate Technical Advisor & Senior Consultant
>>>>> Mobile: +1 253 732 1051
>>>>> Phone: +1 206 331 3833
>>>>> Fax: +1 360 937 9616
>>>>> matthew.adams@xcalia.com
>>>>> P.O. Box 24163
>>>>> Federal Way, WA 98093
>>>>> www.xcalia.com
>>>>>
>>>>> <image.tiff>
>>>>> Xcalia helps businesses address the challenge of Enterprise
>>>>> Information Access in a heterogeneous environment. We provide
>>>>> products and services that facilitate the two-way exchange of
>>>>> information between individuals, mission-critical applications, and
>>>>> databases. Our customers enjoy improved performance, reduced
>>>>> operating and development costs, faster time to market, and
>>>>> rejuvenated legacy systems.
>>>>>
>>>>
>>>
>>>
>>
>>
> Craig Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
>
Re: Database (was: RE: Questions)
Posted by Craig Russell <Cr...@Sun.COM>.
Just to clarify, we want to make it as easy as possible for JDO vendors
to run TCK against all their supported databases. That's why we want
the ddl generator that can be configured by the test run person.
I don't think it makes sense for a compliant JDO implementation to only
run against a SQL92 database.
Craig
On Jan 14, 2005, at 11:51 AM, Brian McCallister wrote:
> For the TCK, it is probably safe to specify any SQL92 compliant
> database, and we are just careful about the DDL. For the
> implementation of JDO it is pointless to only work against one
> database =)
>
> -Brian
>
> On Jan 14, 2005, at 2:40 PM, 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 =) That
>>> said, i would definitely recommend making it really easy to run tests
>>> against any supported database. Ideally a one line config change in
>>> build process, or override via an ant -D switch.
>>>
>>> -Brian
>>>
>>> On Jan 14, 2005, at 1:55 PM, Matthew T. Adams wrote:
>>>
>>>> Hi all,
>>>>
>>>> A few questions:
>>>>
>>>> * When will someone be uploading the next update to the private JDO
>>>> 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?
>>>>
>>>> --matthew
>>>>
>>>> Matthew T. Adams
>>>> Corporate Technical Advisor & Senior Consultant
>>>> Mobile: +1 253 732 1051
>>>> Phone: +1 206 331 3833
>>>> Fax: +1 360 937 9616
>>>> matthew.adams@xcalia.com
>>>> P.O. Box 24163
>>>> Federal Way, WA 98093
>>>> www.xcalia.com
>>>>
>>>> <image.tiff>
>>>> Xcalia helps businesses address the challenge of Enterprise
>>>> Information Access in a heterogeneous environment. We provide
>>>> products and services that facilitate the two-way exchange of
>>>> information between individuals, mission-critical applications, and
>>>> databases. Our customers enjoy improved performance, reduced
>>>> operating and development costs, faster time to market, and
>>>> rejuvenated legacy systems.
>>>>
>>>
>>
>>
>
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Database (was: RE: Questions)
Posted by Brian McCallister <br...@apache.org>.
For the TCK, it is probably safe to specify any SQL92 compliant
database, and we are just careful about the DDL. For the implementation
of JDO it is pointless to only work against one database =)
-Brian
On Jan 14, 2005, at 2:40 PM, 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 =) That
>> said, i would definitely recommend making it really easy to run tests
>> against any supported database. Ideally a one line config change in
>> build process, or override via an ant -D switch.
>>
>> -Brian
>>
>> On Jan 14, 2005, at 1:55 PM, Matthew T. Adams wrote:
>>
>>> Hi all,
>>>
>>> A few questions:
>>>
>>> * When will someone be uploading the next update to the private JDO
>>> 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?
>>>
>>> --matthew
>>>
>>> Matthew T. Adams
>>> Corporate Technical Advisor & Senior Consultant
>>> Mobile: +1 253 732 1051
>>> Phone: +1 206 331 3833
>>> Fax: +1 360 937 9616
>>> matthew.adams@xcalia.com
>>> P.O. Box 24163
>>> Federal Way, WA 98093
>>> www.xcalia.com
>>>
>>> <image.tiff>
>>> Xcalia helps businesses address the challenge of Enterprise
>>> Information Access in a heterogeneous environment. We provide
>>> products and services that facilitate the two-way exchange of
>>> information between individuals, mission-critical applications, and
>>> databases. Our customers enjoy improved performance, reduced
>>> operating and development costs, faster time to market, and
>>> rejuvenated legacy systems.
>>>
>>
>
>
Database (was: RE: Questions)
Posted by "Matthew T. Adams" <ma...@xcalia.com>.
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 =) That
>said, i would definitely recommend making it really easy to run tests
>against any supported database. Ideally a one line config change in
>build process, or override via an ant -D switch.
>
>-Brian
>
>On Jan 14, 2005, at 1:55 PM, Matthew T. Adams wrote:
>
>> Hi all,
>>
>> A few questions:
>>
>> * When will someone be uploading the next update to the private JDO
>> 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?
>>
>> --matthew
>>
>> Matthew T. Adams
>> Corporate Technical Advisor & Senior Consultant
>> Mobile: +1 253 732 1051
>> Phone: +1 206 331 3833
>> Fax: +1 360 937 9616
>> matthew.adams@xcalia.com
>> P.O. Box 24163
>> Federal Way, WA 98093
>> www.xcalia.com
>>
>> <image.tiff>
>> Xcalia helps businesses address the challenge of Enterprise
>> Information Access in a heterogeneous environment. We provide
>> products and services that facilitate the two-way exchange of
>> information between individuals, mission-critical applications, and
>> databases. Our customers enjoy improved performance, reduced
>> operating and development costs, faster time to market, and
>> rejuvenated legacy systems.
>>
>
Re: Questions
Posted by Brian McCallister <br...@apache.org>.
I would suggest Derby or in-memory HSQLDB for system tests =) That
said, i would definitely recommend making it really easy to run tests
against any supported database. Ideally a one line config change in
build process, or override via an ant -D switch.
-Brian
On Jan 14, 2005, at 1:55 PM, Matthew T. Adams wrote:
> Hi all,
>
> A few questions:
>
> * When will someone be uploading the next update to the private JDO
> 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?
>
> --matthew
>
> Matthew T. Adams
> Corporate Technical Advisor & Senior Consultant
> Mobile: +1 253 732 1051
> Phone: +1 206 331 3833
> Fax: +1 360 937 9616
> matthew.adams@xcalia.com
> P.O. Box 24163
> Federal Way, WA 98093
> www.xcalia.com
>
> <image.tiff>
> Xcalia helps businesses address the challenge of Enterprise
> Information Access in a heterogeneous environment. We provide
> products and services that facilitate the two-way exchange of
> information between individuals, mission-critical applications, and
> databases. Our customers enjoy improved performance, reduced
> operating and development costs, faster time to market, and
> rejuvenated legacy systems.
>