Consultor Eletrônico

Status: Unverified

GOAL:

How to do an outer join on the master table of an SDO

FIX:

This must be done using an SDO based upon a temp table.

You should know that using temp-tables with SDOs implies
that you are responsible for all code that builds or
maintains your temp-table and for making sure, based on the issues
indicated above, that you maintain a static list of rowids for the
records contained in it.

This means that the logic for building the temp-table and where this
logic is maintained, is up to you, and is completely out of the scope of
the ADM.

Some people theorize about the best place to put the logic for
populating the temp-table but there is currently no clear prescription
for this from Progress and it is likely that this will always depend on
the specific circumstances of your application.

When your application requires only read access to the records in the
temp-table, and that means there will be no update source for the sdo
and no possibility that the sdo will be used to try and save a
temp-table record, and batching is disabled, it doesn't really matter
whether you run disconnected(stateless or state-reset), state-aware or
Client-Server because the sdo will no longer need to reference the
stored rowids in an attempt to refind the records they once belonged to.

In any other case, you need to think about how you will deploy the code
that is used to maintain the temp-table and where you run the sdo.

This doesn't change the fact that you MUST maintain the maintenance
logic, simply where you deploy it. Sometimes, however, this changes the
context of that logic and how it is written.