You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-dev@db.apache.org by Greg Monroe <Gr...@DukeCE.com> on 2008/01/07 19:07:26 UTC
Some 3.3RC3 Testing results (and failures)
I've been running the Test project with the new 3.3RC3
artifacts against MS SQL 2000 and Derby. The detailed
results are below.
SQL Server passed just fine but the latest version of
Derby won't pass all the tests. I haven't tried older
versions and don't know yet if this is a Torque or Derby
issue.
So, should the Derby problems be considered just a
"Known 3.3RC3 issue" or a show stopper?
I know that Thomas F tested against MySQL and
PostGresSQL. Should 3.3RC3 be checked against DB2
and Oracle as well?
3.3RC3 Testing Results:
Summary:
MS SQL 2000 - passed
Derby 10.3.2.1 Embedded - failed
Derby 10.3.2.1 Network - failed
Details:
MS SQL 2000 with jTDS driver
Test Case 1:
torque.test.base.idMethod = idbroker
torque.generateBeans = true;
torque.useMangers = false;
torque.objectIsCaching = false;
Passed
Test Case 2:
torque.test.base.idMethod = native
torque.generateBeans = false;
torque.useMangers = true;
torque.objectIsCaching = true;
Passed
Test Case 3: (add in Java5 features to #1)
torque.test.base.idMethod = idbroker
torque.generateBeans = true;
torque.useMangers = false;
torque.objectIsCaching = false;
torque.enableJava5Features=true;
Passed (did not check for Java5 warning, just compilation)
Test Case 4: (add in Java5 features to #2)
torque.test.base.idMethod = native
torque.generateBeans = false;
torque.useMangers = true;
torque.objectIsCaching = true;
Passed (did not check for Java5 warning, just compilation)
Derby 10.3.2.1 Embedded
Failed on testJoinOrderDistinct
(The ORDER BY clause may not specify an expression,
since the query specifies DISTINCT.)
Notes:
Tests had to be cut up into separate parts because
some parts of the test don't release the DB for
the next part.
Derby 10.3.2.1 Network Server
Test Case 1:
torque.test.base.idMethod = idbroker
torque.generateBeans = true;
torque.useMangers = false;
torque.objectIsCaching = false;
Failed on testJoinOrderDistinct
(The ORDER BY clause may not specify an expression,
since the query specifies DISTINCT.)
Test Case 2:
torque.test.base.idMethod = native
torque.generateBeans = false;
torque.useMangers = true;
torque.objectIsCaching = true;
Failed on testDoSelectJoinAllExceptY
(Column 'A_ID' cannot accept a NULL value)
Failed on testSingleQuotes
(Column 'A_ID' cannot accept a NULL value)
Failed on testJoinOrderDistinct
(The ORDER BY clause may not specify an expression,
since the query specifies DISTINCT.)
Greg Monroe <Mo...@DukeCE.com> (919)680-5050
C&IS Solutions Team Lead
Duke Corporate Education, Inc.
330 Blackwell St.
Durham, NC 27701
DukeCE Privacy Statement:
Please be advised that this e-mail and any files transmitted with
it are confidential communication or may otherwise be privileged or
confidential and are intended solely for the individual or entity
to whom they are addressed. If you are not the intended recipient
you may not rely on the contents of this email or any attachments,
and we ask that you please not read, copy or retransmit this
communication, but reply to the sender and destroy the email, its
contents, and all copies thereof immediately. Any unauthorized
dissemination, distribution or copying of this communication is
strictly prohibited.
RE: Some 3.3RC3 Testing results (and failures)
Posted by Greg Monroe <Gr...@DukeCE.com>.
After testing with Derby some more, I found that
the "Column 'A_ID' cannot accept a NULL value"
errors were actually being caused by Derby not
being able to drop and existing table (circular
foreign key reference).
So, the table was not being created with native
autoincrement settings. This was causing the error
to occur. (This was compounded on my part by some
missconfigured Derby settings that made me think
I had deleted the DB files between runs when it
actually hadn't been done.)
There is still the problem with "the ORDER BY
clause may not specify an expression, since the
query specifies DISTINCT". I've tracked this down
to Derby not allowing for selects like:
SELECT DISTINCT author.author_id, author.name,
UPPER(author.name)
FROM author INNER JOIN book ON
author.author_id=book.author_id
ORDER BY UPPER(author.name) ASC
The problem is the UPPER function. Not sure there
is a way to fix this easily. But IMHO this specific
problem isn't a show stopper.
> -----Original Message-----
> From: Greg Monroe [mailto:Greg.Monroe@DukeCE.com]
> Sent: Monday, January 07, 2008 1:07 PM
> To: Apache Torque Developers List
> Subject: Some 3.3RC3 Testing results (and failures)
>
> I've been running the Test project with the new 3.3RC3
> artifacts against MS SQL 2000 and Derby. The detailed
> results are below.
>
> SQL Server passed just fine but the latest version of
> Derby won't pass all the tests. I haven't tried older
> versions and don't know yet if this is a Torque or Derby
> issue.
>
> So, should the Derby problems be considered just a
> "Known 3.3RC3 issue" or a show stopper?
>
> I know that Thomas F tested against MySQL and
> PostGresSQL. Should 3.3RC3 be checked against DB2
> and Oracle as well?
>
> 3.3RC3 Testing Results:
>
> Summary:
>
> MS SQL 2000 - passed
> Derby 10.3.2.1 Embedded - failed
> Derby 10.3.2.1 Network - failed
>
> Details:
>
> MS SQL 2000 with jTDS driver
> Test Case 1:
> torque.test.base.idMethod = idbroker
> torque.generateBeans = true;
> torque.useMangers = false;
> torque.objectIsCaching = false;
>
> Passed
>
> Test Case 2:
> torque.test.base.idMethod = native
> torque.generateBeans = false;
> torque.useMangers = true;
> torque.objectIsCaching = true;
>
> Passed
>
> Test Case 3: (add in Java5 features to #1)
> torque.test.base.idMethod = idbroker
> torque.generateBeans = true;
> torque.useMangers = false;
> torque.objectIsCaching = false;
> torque.enableJava5Features=true;
>
> Passed (did not check for Java5 warning, just compilation)
>
>
> Test Case 4: (add in Java5 features to #2)
> torque.test.base.idMethod = native
> torque.generateBeans = false;
> torque.useMangers = true;
> torque.objectIsCaching = true;
>
> Passed (did not check for Java5 warning, just compilation)
>
> Derby 10.3.2.1 Embedded
>
> Failed on testJoinOrderDistinct
> (The ORDER BY clause may not specify an expression,
> since the query specifies DISTINCT.)
>
> Notes:
> Tests had to be cut up into separate parts because
> some parts of the test don't release the DB for
> the next part.
>
> Derby 10.3.2.1 Network Server
>
> Test Case 1:
> torque.test.base.idMethod = idbroker
> torque.generateBeans = true;
> torque.useMangers = false;
> torque.objectIsCaching = false;
>
> Failed on testJoinOrderDistinct
> (The ORDER BY clause may not specify an expression,
> since the query specifies DISTINCT.)
>
> Test Case 2:
> torque.test.base.idMethod = native
> torque.generateBeans = false;
> torque.useMangers = true;
> torque.objectIsCaching = true;
>
> Failed on testDoSelectJoinAllExceptY
> (Column 'A_ID' cannot accept a NULL value)
> Failed on testSingleQuotes
> (Column 'A_ID' cannot accept a NULL value)
> Failed on testJoinOrderDistinct
> (The ORDER BY clause may not specify an expression,
> since the query specifies DISTINCT.)
>
> Greg Monroe <Mo...@DukeCE.com> (919)680-5050
> C&IS Solutions Team Lead
> Duke Corporate Education, Inc.
> 330 Blackwell St.
> Durham, NC 27701
>
>
>
>
>
> DukeCE Privacy Statement:
> Please be advised that this e-mail and any files transmitted with
> it are confidential communication or may otherwise be privileged or
> confidential and are intended solely for the individual or entity
> to whom they are addressed. If you are not the intended recipient
> you may not rely on the contents of this email or any attachments,
> and we ask that you please not read, copy or retransmit this
> communication, but reply to the sender and destroy the email, its
> contents, and all copies thereof immediately. Any unauthorized
> dissemination, distribution or copying of this communication is
> strictly prohibited.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org