One more APEX question - Developing Schemas vs. Live Production Application Schemas?
From: Chris Taylor <christopherdtaylor1994_at_gmail.com>
Date: Tue, 26 Jul 2016 11:47:50 -0500
Message-ID: <CAP79kiRCr-k7w6NQZqBvvzgYPRUh+a8Fut3S4W9NL4QTNMLm+g_at_mail.gmail.com>
Let's say I create a WORKSPACE in my Development APEX environment and Joe Developer creates an application there in his workspace.
Date: Tue, 26 Jul 2016 11:47:50 -0500
Message-ID: <CAP79kiRCr-k7w6NQZqBvvzgYPRUh+a8Fut3S4W9NL4QTNMLm+g_at_mail.gmail.com>
Let's say I create a WORKSPACE in my Development APEX environment and Joe Developer creates an application there in his workspace.
All the objects for his application are owned by his database ID - JDEVMAN and are stored in their own tablespace.
Now, Joe is ready to migrate his app to Production AND he kindly exports it for me, the Administrator.
Now, do I import it into a generic APP Schema that I create in Production? Cause I don't think Joe is going to have his own Workspace in Production, right?
I'm just unclear (and looking for clarifications) on what Joe's Application looks like in DEV versus what it's going to look like in Prod.
I'm imagining his Application would have it's own schema & workspace in Production but maybe I'm wrong?
Chris
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Jul 26 2016 - 18:47:50 CEST