Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Developers List" <torque-dev@db.apache.org>
Received-SPF: pass (athena.apache.org: domain of greg.monroe@dukece.com
 designates 152.3.166.24 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Some 3.3RC3 Testing results (and failures)
Date: Mon, 7 Jan 2008 18:10:18 -0500
Message-ID: <8F5843B903F59D4C8C6806BB49A39119051FC792@dukece-mail3.dukece.com>
In-Reply-To: 
 <8F5843B903F59D4C8C6806BB49A39119051FC47D@dukece-mail3.dukece.com>
Thread-Topic: Some 3.3RC3 Testing results (and failures)
Thread-Index: AchRWCkAahcTXMU+RQCu6pGFnmVFwAAKIScg
References: <8F5843B903F59D4C8C6806BB49A39119051FC47D@dukece-mail3.dukece.com>
From: "Greg Monroe" <Greg.Monroe@DukeCE.com>
To: "Apache Torque Developers List" <torque-dev@db.apache.org>

After testing with Derby some more, I found that=20
the "Column 'A_ID'  cannot accept a NULL value"=20
errors were actually being caused by Derby not=20
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=20
missconfigured Derby settings that made me think=20
I had deleted the DB files between runs when it=20
actually hadn't been done.)

There is still the problem with "the ORDER BY=20
clause may not specify an expression, since the=20
query specifies DISTINCT".  I've tracked this down
to Derby not allowing for selects like:

SELECT DISTINCT author.author_id, author.name,=20
   UPPER(author.name)=20
FROM author INNER JOIN book ON=20
   author.author_id=3Dbook.author_id=20
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=20
problem isn't a show stopper.

> -----Original Message-----
> From: Greg Monroe [mailto:Greg.Monroe@DukeCE.com]=20
> Sent: Monday, January 07, 2008 1:07 PM
> To: Apache Torque Developers List
> Subject: Some 3.3RC3 Testing results (and failures)
>=20
> I've been running the Test project with the new 3.3RC3
> artifacts against MS SQL 2000 and Derby.  The detailed=20
> results are below.
> =20
> SQL Server passed just fine but the latest version of=20
> 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=20
> issue.
> =20
> So, should the Derby problems be considered just a
> "Known 3.3RC3 issue" or a show stopper?
> =20
> I know that Thomas F tested against MySQL and=20
> PostGresSQL.  Should 3.3RC3 be checked against DB2
> and Oracle as well?
> =20
> 3.3RC3 Testing Results:
>  =20
> Summary:
>  =20
>    MS SQL 2000 - passed
>    Derby 10.3.2.1 Embedded - failed
>    Derby 10.3.2.1 Network  - failed
>   =20
> Details:
> =20
>   MS SQL 2000 with jTDS driver
>     Test Case 1: =20
>       torque.test.base.idMethod =3D idbroker
>       torque.generateBeans =3D true;
>       torque.useMangers =3D false;
>       torque.objectIsCaching =3D false;
>      =20
>       Passed
>      =20
>     Test Case 2:
>       torque.test.base.idMethod =3D native
>       torque.generateBeans =3D false;
>       torque.useMangers =3D true;
>       torque.objectIsCaching =3D true;
>      =20
>       Passed=20
> =20
>     Test Case 3: (add in Java5 features to #1)
>       torque.test.base.idMethod =3D idbroker
>       torque.generateBeans =3D true;
>       torque.useMangers =3D false;
>       torque.objectIsCaching =3D false;
>       torque.enableJava5Features=3Dtrue;=20
>      =20
>       Passed (did not check for Java5 warning, just compilation)
>      =20
>=20
>     Test Case 4: (add in Java5 features to #2)
>       torque.test.base.idMethod =3D native
>       torque.generateBeans =3D false;
>       torque.useMangers =3D true;
>       torque.objectIsCaching =3D true;
>      =20
>       Passed (did not check for Java5 warning, just compilation)
>      =20
>   Derby 10.3.2.1 Embedded
> =20
>     Failed on testJoinOrderDistinct=20
>         (The ORDER BY clause may not specify an expression,=20
>           since the query specifies DISTINCT.)
>          =20
>     Notes:=20
>       Tests had to be cut up into separate parts because=20
>       some parts of the test don't release the DB for=20
>       the next part.
>    =20
>   Derby 10.3.2.1 Network Server
>  =20
>     Test Case 1: =20
>       torque.test.base.idMethod =3D idbroker
>       torque.generateBeans =3D true;
>       torque.useMangers =3D false;
>       torque.objectIsCaching =3D false;
> =20
>       Failed on testJoinOrderDistinct
>         (The ORDER BY clause may not specify an expression,=20
>           since the query specifies DISTINCT.)     =20
>          =20
>     Test Case 2: =20
>       torque.test.base.idMethod =3D native
>       torque.generateBeans =3D false;
>       torque.useMangers =3D true;
>       torque.objectIsCaching =3D true;
>          =20
>       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,=20
>           since the query specifies DISTINCT.)
> =20
> Greg Monroe <Monroe@DukeCE.com> (919)680-5050
> C&IS Solutions Team Lead
> Duke Corporate Education, Inc.
> 330 Blackwell St.
> Durham, NC 27701
>=20
>=20
> =20
>=20
>=20
> 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.
>=20

---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org