ArcGIS Pro 2.9.5; Oracle 18c 10.7.1 enterprise geodatabase
I have a ROADS line FC and an EVENTS standalone table. The relationship of the underlying data is one-to-many: one road to many events. No relationship class. Both registered with the geodatabase.
If I use the Add Join tool to create a join from ROADS to EVENTS, the join’s relationship will be one-to-many. That works as expected.
However, if I create a database view (not registered with the geodatabase) on EVENTS called EVENTS_VW [SELECT * FROM EVENTS], and join from ROADS to EVENTS_VW, then the relationship of the join is one-to-first, not one-to-many. That’s not expected.
The Add Join documentation says the data needs to have OBJECTIDs and needs to be located in the same workspace (same geodatabase) in order for a one-to-many join to be automatically created. The database view meets those requirements. So why does the view behave differently from the standalone table?
(I don’t want to register the view with the geodatabase because that makes it too difficult to make changes to the view in the future. I’d need to delete the view, recreate the view, reregister the view with the GDB, and re-do all the database privileges. That’s not a good use of time.)
