Re: PeopleSoft and Referential Integrity

In article <33eaf636.9821449_at_news.dircon.co.uk>, Phil Edwards <news-uk_at_dircon.co.uk.nojunk> wrote:
>On Fri, 08 Aug 1997 01:58:42 GMT, twincrk_at_ral.mindspring.com (S.
>Fleming) wrote:
>
>>To be perfectly honest, I am a PeopleSoft developer with somewhat
>>limited Oracle skills so I really don't know what you are asking.
>>However, when you generate a SQL script from the Data Designer you get
>>something like the one shown below. The only parameters that
>>PeopleSoft lets you change in the Data Designer are the init and next
>>sizes and the tablespace name. Those changes are saved and
>>automatically placed in the script when the script is generated again.
>
>< script snipt >
>
>The answer is: PeopleSoft's generated DDL doesn't use declarative RI
>(the script used CREATE UNIQUE INDEX rather than a CONSTRAINT clause)
>and you can't change it to make it do so.
>
>Phil
>--
>Phil Edwards phil_at_news400.com
>Editor, NEWS/400.uk +44 (0)161 929 0777

OK, it appears that PeopleSoft does not use declarative RI. Oracle allows for a table to be altered after it is created. For parent (prompt) tables that do not have effective dating it should be possible to read the PeopleSoft Tools tables and create scripts that add declarative RI. For tables with effective dating the typical solution is to create a synthetic key and use that for joining the tables.

I have tried to reverse engineer the tools tables by looking for columns with the word join in the name. I found a few but they were numbers not names. Does anyone have an explanation of how the tools tables work?

Also has anyone tried to use People Code to use synthetic keys for joining?

Any help would be greatly appreciated

mjr Received on Tue Aug 12 1997 - 00:00:00 CDT