RE: Identity value of 0 -- MIDRANGE-L

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

The journal proved that the ID value was set when the row was written, but an update operation shortly thereafter set the ID to 0. I would have expected the update to blow up when it tried that.

-----Original Message-----
From: Paul Bailey [mailto:PabloMotte+Midrange@xxxxxxxxx]
Sent: Tuesday, February 06, 2018 11:19 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Identity value of 0

I didn't think that was possible either. A pair of ideas:
- Was the file restored recently? There has been discussion recently on this list about unexpected value in an ID column, but I didn't see mention of a zero value in the ID column.
- If you have a journal attached, can you see the job/program that created the rows? My thought would be that someone inserted a row specifying zero as the ID column, but I thought that was impossible too. If it was possible then an insert with a subselect, or a plain insert, might do it if you don't specify "default" as the column value (or leave it out of the insert column list).

HTH
Paul.

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.