×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
We're still on v7r1 here. How does the new 12 digit precision affect
timestamp fields in tables defined prior to v7r2? With the additional 6
digits, I presume that more space is needed to store them than before.
Also, because when you absolutely, positively must have a unique key but
can't rely on a timestamp (even with 12 digit precision for the second!) to
provide it, what was the impetus to increase the precision? Curious
mind(s?) wants to know.
(Interesting story about GM and the COBOL compiler, Jon!)
- Dan
On Thu, Apr 16, 2015 at 5:42 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:
At 7.2 the timestamp precision has been increased - you can now go up to
12 digits in the fraction of seconds.
We're not yet on 7.2, so it'd interesting to hear the experience of others
in this.
Vern
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
