This content has been marked as final. Show 3 replies
You can create another COLUMN - ATTRIBUTE mapping in the configuration file for "id"
That would be the obvious solution, but it doesn't work... OPA complains it is already defined. Hence, my question.
Perhaps better, if you could give me a sample xml config with global and one entity. The only attribute in the entity should be the id... The id should be the primary key in both OPA and Oracle...
The global table in oracle would contain a single column with the global id.
The child table in oracle would contain 2 columns -> one for the global ref id and one for the child key...
I think you will find problems.
As a note we have duct-tape solved this by creating views and making column copies in the views of the child id and then mapping the id in oracle to the duplicate column in the view.
So our child view contains the child table with the child id repeated twice so that we can map...