Note: With Multi-Row Fetch rows wouldn’t have unique timestamps if the timestamps WERE generated at fetch time.
Cheers, Martin Sent from my iPad > On 28 Mar 2019, at 19:15, Paul Gilmartin <0000000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > > On Thu, 28 Mar 2019 11:38:24 -0700, Sri h Kolusu wrote: > >>> I'm astonished; I'd expect data bases to log times of transactions. Or is >>> that left the responsibility of the UI/API? >> >> When I say DB2 gives a static timestamp is when you are trying to get >> EXISTING records from a DB2 table and append a time stamp. ... >> > OK. I RTFM. The term it uses in a few places is "time of the run". I'm > happy that means the time of the SELECT rather than time of the FETCH. > May I assume, since neither you nor Bernd said otherwise, that insertion > of a row will use the instantaneous timestamp? > > And disappointed, that the format has a granularity of at best µsec, > sacrificing the uniqueness of the (E)TOD clock. Not an issue > unless/until processors are fast enough to perform more than one > transaction in that time. > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
