db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Monroe" <Greg.Mon...@DukeCE.com>
Subject Some 3.3RC3 Testing results (and failures)
Date Mon, 07 Jan 2008 18:07:26 GMT
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 <Monroe@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.
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message