in one of the previous posts was mentioned "a wrapper business object" that would allow to create a business object having data/columns from several tables.
The BusinessObject = 1 table is slightly problematic in the case when you would need to create a business object that would include columns from several tables (a SQL join) and perhaps some computed fields (some computation rather done in the database than in the application).
In a Oracle environment would a) this kind of wrapper solve this problem orb) DDT bring any help on this issuec) something else...? Lastly, is this true: the data structure of the business object is just a place holder and the query populating the data structure can be whatever, e.g any SQL-statement? If this true, then it would be possible to create just some dummy tables/views into the database. However, a wrapper approach would perhaps be "cleaner" as it wouldn't add anything to the database.
Kari
ok, so this would require the use of DDT and as such there is now way to "combine" two business objects. Therefore - in Oracle world - the same can be achieved by just creating a table with the required "business object"-layout. The result is not optimal as it results in creating objects in the database that are not required.
It would be nice if a business object could be based on a SQL-statement...Kari
The reason this would not work is due to the update. This is really no different than a view...however, a view can be updatable which would support the logic behind INSERTs and UPDATEs.