Re: separate DEV, TEST, & PROD environments survey -- MIDRANGE-L

Subject: Re: separate DEV, TEST, & PROD environments survey
From: Nathan Andelin <nandelin@xxxxxxxxx>
Date: Wed, 4 Sep 2013 16:49:37 -0700 (PDT)
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>

From: Charles Wilt
For that matter, every single RDBMS I'm familiar with only allows a single level
of schemas.

I gather that you mean the "catalog" or "database" parameter referenced on RDBMS "connection" strings. At any rate, I like the analogy. They don't offer an option to define or connect to a database within a database within a database. Likewise, IBM i doesn't offer an option to define or connect to a library within a library within a library (with the exception of QSYS).

Referencing files and other objects within IBM i libraries is essentially similar to referencing RDBMS objects within a "catalog" or "database".

-Nathan

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: separate DEV, TEST, & PROD environments survey , franz400
Re: separate DEV, TEST, & PROD environments survey , Mark S Waterbury

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.