|
How do the other Spaces folks connect to the database?
On Thu, Jul 7, 2016 at 5:29 PM, Aaron Bartell <aaronbartell@xxxxxxxxx>
wrote:
andI don't know what my database is, and I'm not sure if I know what mypassword is.
Select the 'i' icon on your Spaces home page and you will see your user
three separate databases (schemas, libraries).
We have to be a little careful about terminology here. In an IBM
midrange context, "database" is not the same thing as "schema", though
it is pretty safe to use "schema" and "library" interchangeably.
A database at a typical IBM i shop contains many libraries, though I
suppose there is nothing preventing you from having a database which
contains just one library.
Are you saying that each of those three environments is its own
*database*, and that the names shown are the database names, as would
appear when entering the DSPRDBDIRE command at a native CL prompt?
Litmis Spaces operates off of passwordlessness (new word? :-) What Imean
is we definitely have passwords for IBM i profiles, but they are randomly
generated and not stored. Instead we opted to go with ssh keys for all
authentication into the machine.
That's a perfectly reasonable arrangement. It's probably what I would
opt for if I were setting up a similar service. But it creates the
issue of how to retrieve a password so that it can be used as a
parameter to the ibm_db.connect() method.
How do the other Spaces folks connect to the database?
John Y.
--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/opensource.
As an Amazon Associate we earn from qualifying purchases.
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.