Re: Using SQL SEQUENCE for Next Number Operations -- MIDRANGE-L

Subject: Re: Using SQL SEQUENCE for Next Number Operations
From: CRPence <CRPbottle@xxxxxxxxx>
Date: Sun, 20 Oct 2013 15:18:18 -0700
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>

On 10/20/13 2:14 PM, Vernon Hamberg wrote:

<<SNIP>> I believe that with *SQL naming, JDBC driver can be set to
use more than the "user name" library - take a look at the JDBC
settings in the SQL statement processor in Navigator for an example.

Take care not to confuse the CURRENT PATH with the CURRENT SCHEMA.

The unqualified sequence will be "implicitly qualified by the default schema" [though testing shows /current schema/ as qualifier instead]. The unqualified sequence-name is *not* located via the PATH. The default schema for *SYS naming is the library list (*LIBL). There is no similar Library List concept in the *SQL naming for the SCHEMA, only for the PATH.

Follow-Ups:

Re: Using SQL SEQUENCE for Next Number Operations , Vernon Hamberg

This mailing list archive is Copyright 1997-2026 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.