This content has been marked as final. Show 4 replies
Are you stuck doing the design like this? If not, I would highly recommend splitting things so that what's in the object becomes a separate table with foreign keys back to the main table. Makes things much more manageable, maintainable and easier to query!
This is a legacy application and the design is already in use so cant change it now .
Nested object type attributes can be referred to with simple dot notation. However this is slightly obscured by the fact that a table alias is required for name resolution. Hopefully the following example will help...
SELECT bi.sk_booking_id FROM booking_iteration bi WHERE bi.booking_calc.product_id = 101;
thanks everybody. Spot on.