Keep cool. When working with a community, is normal to get some messages of all kind. AFAIK, I've not worked with IBM DB2, but all databases has a TIMESTAMP like data type, and some has no capabilities for millisecond (as example, some databases like MS SQL Server store with 1000/3 milliseconds precision in a DATETIME datatype fields). I'm using OJB with SapDB, and I get all info from database without any problems (including milliseconds information), so I think you should double-check:
1) Your database capabilities. What datatype is for the job, and what is the limitations. 2) If you JDBC driver has some kind of known bug. There are a lot of ones in all drivers around, and I don't think DB2 JDBC driver has none. 3) You could publish a test case so people actively working on OJB can make tests to know if it's a bug, and add your test case into main test routines. Every time I stop and write a test case, I've discovered something wrong I'm doing... 4) If the OJB implmementation (or layer) for DB2 has some buggy code (here is some good bugs too - just download sources and debug! It's not so hard and will give back to community valuable resources!). Best regards, Edson Richter ----- Original Message ----- From: Gopi Nandamuri To: OJB Users List Sent: Thursday, January 15, 2004 6:27 AM Subject: RE: TimeStamp & Error Codes First of all did you understand what my mail is for? If I don't know what OJB is for I might not have even tried to test that one and not wasted your valuable time. There are four points in my mail and all are valid ones. If you don't know what I meant don't even try to answer. Thanks -----Original Message----- From: Guillaume Nodet [mailto:[EMAIL PROTECTED] Sent: 14 January 2004 20:50 To: OJB Users List Subject: RE: TimeStamp & Error Codes Considering your mail, i'm not sure you have completely understood what OJB is for. What do you want to use it for ? -----Message d'origine----- De : Gopi Nandamuri [mailto:[EMAIL PROTECTED] Envoye : mercredi 14 janvier 2004 16:34 A : OJB Users List Objet : RE: TimeStamp & Error Codes Hi All, Can anyone reply to my message? In question 1 I have wrongly mentioned time in Nano seconds but I am looking up to microseconds. Using JavaDate2SqlTimestampFieldConversion class I am able to convert java.util.Date to TimeStamp, but in microseconds it is moving zeroes. I am using IBMWebSphere as my application server and I am trying to use p6spy. I have changed build.properties file to add usep6spy=true and changed spy.properties file to accept DB2 Jdbc driver and the location of log file. But that seems to be not working. Can anyone point out where I am missing? Thanks & Regards, Gopi. -----Original Message----- From: Gopi Nandamuri Sent: 14 January 2004 10:48 To: [EMAIL PROTECTED] Subject: TimeStamp & Error Codes Hi, 1) I am new to OJB and Testing OJB with various options to suit my database. I have a TimeStamp field in my table and I would like to enter the exact time (In Nano Seconds) when I call the Store method in broker. In SQL we used to do like this insert into table values (TIMESTAMP,...). Is there any equivalent of this in OJB? I am using org.apache.ojb.broker.PersistenceBroker. (I don't want to call java.sql.TimeStamp constructor by passing the arguments to construct the timestamp object) 2) In jdbc the return type of preparedStatement.executeUpdate() method gives the no of rows updated or inserted. By checking the return type we can say that the operation was successful or not. In OJB we have the object and we will call store or delete methods. Is there a way to know whether that operation was successful or not? If there is an error, is it possible to find out the SQLErrorCode for that error like SQLException.getErrorCode() ? Thanks & Regards, Gopi. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.561 / Virus Database: 353 - Release Date: 13/1/2004 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
