Re: [OJB-developers] JUNIT failures & errors

[Thomas M. <tho...@ho...>]

Hi Jakob,

Jakob Braeuchi wrote:

> hi thomas,
> 
> 
>>This may work in most situations, but it does not work for Update
>>statements in Hsqldb (AFAIK DB2 and InstantDB also don't support this).
>>
> 
> this is one of the main problems when dealing with multiple databases, i use
> mysql as test database and there it works.


I agree!


> for some tests i also use ms-access but i never worked with hsqldb.
> we need some kind of test platform, where we can run accesslayer-code
> against _all_ supported databases.
> 


Yes, that would be the best solution.
But at my company I only have access to DB2, Oracle, MS-Access, and 
Hypersonic.

Licencing RDBMS is expensive ! It's also a know-how problem. I don't 
feel like learning about admistrating say Informix.

Maybe we can set up a kind of "distributed test farm" ?
Maybe it would be easier to just share the reponsibilities for testing 
against special platforms,
say:
Jakob : MySql
Thomas: HsqlDb, DB2
...
...

cheers,

thomas


> jakob
> 
> ----- Original Message -----
> From: "Thomas Mahler" <tho...@ho...>
> To: "ojb" <obj...@li...>
> Sent: Sunday, June 02, 2002 4:22 PM
> Subject: [OJB-developers] JUNIT failures & errors
> 
> 
> 
>>Hi all,
>>
>>I just checked in some minor fixes that cure most of the problems I
>>mentioned in my last mail.
>>
>>I set some log-messages in JdbcAccess from .error(...) to .debug(...).
>>This avoids all the internal stacktrace within the PB Junit tests.
>>This does not compromise stability as throwing of exceptions is not
>>
> touched.
> 
>>I found a minor issue in SqlUpdateStatement:
>>in appendSetClause(...) it uses appendColname from the baseclass
>>SqlStatement.
>>
>>This method is used to generate column names from field descriptors.
>>It uses FieldDescriptor.getFullColumnName() to build a column name.
>>This will include Schema and table name in a column name (i.e. a column
>>"NAME" would be fullqualified as "MySchema.MyTable.NAME").
>>
>>This may work in most situations, but it does not work for Update
>>statements in Hsqldb (AFAIK DB2 and InstantDB also don't support this).
>>
>>I refactored this code with the "template method" pattern, that allows
>>subclasses to override the qualification behaviour.
>>
>>Could this fix be problematic for other databases? Or could there be any
>>cases where full-qualified names are needed within Update Statements?
>>
>>Now we have the following JUnit results:
>>PersistenceBroker: 0 Failures, 0 Errors, 0 Stacktraces
>>SODA: 0 Failures, 0 Errors, 0 Stacktraces
>>ODMG: 0 Failures, 1 Error (resulting in some stacktracing)
>>
>>The error is in test.ojb.odmg.OneToOneTest.testSave().
>>
>>I hope to get this fixed soon.
>>
>>cheers,
>>
>>Thomas
>>
>>
>>_______________________________________________________________
>>
>>Don't miss the 2002 Sprint PCS Application Developer's Conference
>>August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
>>
>>_______________________________________________
>>Objectbridge-developers mailing list
>>Obj...@li...
>>https://lists.sourceforge.net/lists/listinfo/objectbridge-developers
>>
>>
> 
> _______________________________________________________________
> 
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
> 
> _______________________________________________
> Objectbridge-developers mailing list
> Obj...@li...
> https://lists.sourceforge.net/lists/listinfo/objectbridge-developers
> 
> 
> 
>