On Wed, 2006-03-29 at 17:08 +0200, Bram Kuijvenhoven wrote: > > After install the snapshot version I had success in doing a browse in > > DB2 tables. There was new errors that I report below in the way people > > can try to fix them: > > > > 1. Any update in table(via INSERT, UPDATE or DELETE) generates a empty > > Message Dialog. I'm talking about an application developed with > > DBNavigator and DBGrid; > > [Joost/Michael:] Does this need an implementation of ApplyUpdates in > TODBCConnection?
No. Applyupdates is handled at the TSQLQuery-level. I need more information to see what's going wrong here. > > 2. People that uses DB2 in mainframe applications has the habit of use > > TIMESTAMP fields as keys to make relation between tables. The format of > > TIMESTAMP that is returned isn't useful since it eliminates the 6 digit > > fractions of second. When you download the data from mainframe to DB2 > > tables in the low platform it's necessary to keep mainframe format > > compatibility because there are COBOL environments that emulate > > mainframe behavior. The idea of these cobol environments is test in the > > low platform and upload the sources, compile, catalog and run > > applications on mainframe without new tests. More over it must be > > thousands of other applications that would benefit of DB2 TIMESTAMP > > format. BTW, the format of TIMESTAMP in DB2 is YYYY-MM-DD > > HH.MM.SS.UUUUUU. IMHO, any other format seems to be not correct for DB2 > > approach. > > This sounds quite obscure to me; are those timestamps used as /unique/ keys? > > It would require some investigation to find out whether it is possible at all > to do this. In the first place it would require a TTimeStamp implementation. > Secondly, the ODBC driver should be capable of passing information about the > precision of the timestamp. Thirdly, the TTimeStamp implementation would be > required to support this precision information as well. Finally, it should > somehow be possible to present the TTimeStamp in the YYYY-MM-DD > HH.MM.SS.UUUUUU format in the GUI controls you use. > > I will take a look at the capabilities of ODBC to pass precision or format > information of columns/data types. It's a completely new approach for me also. A solution could be to cast the timestamp to a string in the query. Like : select cast(time,varchar) from table; in Oracle. I'm sure that also has a mechanism for that. -- Met vriendelijke groeten, Joost van der Sluis CNOC Informatiesystemen en Netwerken http://www.cnoc.nl _________________________________________________________________ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
