Re: (SQL) Identity Crisis -- MIDRANGE-L

Subject: Re: (SQL) Identity Crisis
From: Mark S Waterbury <mark.s.waterbury@xxxxxxxxxxxxx>
Date: Fri, 05 Apr 2013 14:55:40 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Rob:

RTFA (Read The Fine Article)... it's in there.

When you use the "NEXT VALUE FOR sequence-Name" clause in an SQL statement, the value is incremented (e,g, inserting into ORDHDR). To refer to the same value previously generated, you use the "PREVIOUS VALUE FOR sequence-Name"" (e.g. when inserting into ORDDTL).

You have control over when the value is incremented, because you may want to use the same value as the "key" for example for in ORDHDR and ORDDTL "parent-child" set of tables.

Can you dig it?

HTH,

Mark S. Waterbury

> On 4/5/2013 2:43 PM, rob@xxxxxxxxx wrote:

And how does that automatically increment upon an insert?

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: (SQL) Identity Crisis , rob

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.