Re: Database file reorg

Even if it is not used as a key, the time can be used to sort the
records "in arrival sequence"

Having the processor speeds stuck at around 4 GH, for so long, seems
that faster are far in the future, but you can have several processors
writing.

By default RPG uses only 3 decimal digits for seconds, which is not
enough. But leaving SQL to write the timestamp you can have to to 12
decimals (pico seconds), even if current hardware only gives you 9 (nano
seconds) reliable digits. 

On 8/16/19 10:26 AM, Rob Berendt wrote:

Database purists will argue that a time should not be used as a key in a log file. The main logic being how many decimal places of the seconds do you support? How many does your application really support? For example does RPG support all of them or does it default the last few to zeros? Did it used to in the past? And, that time may work now but what happens when you get even faster hardware, etc? Meaning, can you theoretically belt out more than a single transaction in the same timestamp?

Rob Berendt

-- Este e-mail fue enviado desde el Mail Server del diario ABC Color --
-- Verificado por Anti-Virus Corporativo Symantec --