× 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.


  1.  Home
  2. RPG400-L
  3. July 2015

Re: duplicate key error in identity column

On Thu, Jul 16, 2015 at 11:22 AM, Birgitta Hauser
<Hauser@xxxxxxxxxxxxxxx> wrote:
Native I/O should fully support all precisions, despite what limitations
any HLL might have for timestamp support

Just try to fill a timestamp variable with 12 microseconds with the RPG
built-in-Function %Timestamp() or Display DSPLY %Timestamp(*SYS: 12).

Birgitta, I think you have not read Chuck's post carefully enough. He
is saying that any failure to utilize the full precision of the
timestamp is a limitation in the programming language. In the context
of this discussion, he is saying that RPG doesn't support the full
precision, but other HLLs are free to support as much or as little
precision as they wish.

After fill the same variable with the SQL special register.
I'm quite sure in the first case the result looks like:
YYYY-MM-DD-HH-MI-SS.XXX000000000000 and in the second case all digits are
filled.

And you have precisely illustrated Chuck's point.

John Y.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.