Skip to Main Content
Forums

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Maintaining data & data schema between Development vs Production?

DannyS-OracleJun 15 2017 — edited Jun 16 2017

Hi everyone, I am a beginner Apex developer and need some advice on how to sync between my development and production instances. I tried searching on this forum, and this has been asked before here , but there was no feedback.

So my situation is, we are planning to have two different instance of our application:

  1. Development, where we do all experiment and add new features; and
  2. Production, where we put all stable features, production data, and make it accessible for our users.

We are thinking to put these two instances on different workspaces, so we can safely export and import all pages easily and separate development vs production data.

The case where I am concerned is, how to keep the data schema between the development and production workspaces in sync? Let's say I implemented some features in dev environment, where I need to make changes to certain table (e.g. adding/removing columns or triggers in Table A). How to reflect this changes automatically in the production environment? I believe I can't just export the data, replace the data schema with the one from dev, and then re-import the data because some table columns might have changed. Do I have to implement all those changes manually in the production workspace?

Please let me know if you have been in similar situation, or if you know better solution for this. Any feedback will be appreciated! I am using Apex v5.1, Oracle DB v12.

Comments

Anurag Tibrewal
Hi,

With whatever requirement you posted so far, it is possible.
You need to write a dml trigger (insert/update/delete) on the table1. Inside the trigger you would be writing a code to do the changes on table2.
Points to remember
- schemaA(where table1 resides) needs the direct insert/update/delete privilege on table2 of schemaB.
- Prefix schema name with table2 inside the trigger.

Regards
Anurag
1 person found this helpful
Knightbeat
Thank you so much, for the reply.

I can't even imagine how did you reply so quickly! I think my question was 100% answered, and now I can surf to know how it can be done, as I now know that It's possible to be done!

Thank you very much! I really appreciate your generosity!
1 - 2
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Jul 13 2017
Added on Jun 15 2017
#apex-discussions, #data, #database, #schema, #workspace
3 comments
1,229 views