From: twincrk@ral.mindspring.com (S. Fleming) Subject: Re: PeopleSoft and Referential Integrity Date: 1997/08/08 Message-ID: <5sdutv$80u@camel2.mindspring.com>#1/1 References: <5rsrhq$1gv@camel1.mindspring.com> X-Server-Date: 8 Aug 1997 02:05:51 GMT Organization: MindSpring Enterprises, Inc. Reply-To: twincrk@ral.mindspring.com Newsgroups: comp.databases,comp.databases.oracle.misc >mjr@netcom.com (Mark Rosenbaum) wrote: >Sorry for the confusion. To me more precise I would like to know if >it is possible to turn on DATABASE Referential Integrity using >PeopleSoft. My understanding is that PeopleSoft actually creates >the DDL to create the tables but does not define Primary keys >and Foreign Keys. The PeopleSoft HR app running on Oracle that >I am currently working on has no PK FK constraints. >I have also been told that you can change the PS DDL but every time >there is a PS change you would then have to reedit the scripts. >So my question is >Is there a module or a switch or anything in PeopleSoft that would >allow you to easily turn on Referential Integrity at the data base >level? >TIA 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. remark Create Dept_Est_Tbl_HM; remark Recreate Estab_Tbl to add a new field; remark Create View Dept_Sec_Src_Hm; remark Generated by Steve Fleming on 03/27/96; CREATE TABLE PS_DEPT_EST_TBL_HM (DEPTID VARCHAR2(10) NOT NULL, EFFDT DATE NOT NULL, EFF_STATUS VARCHAR2(1) NOT NULL, ESTABID VARCHAR2(5) NOT NULL) TABLESPACE HTAPP STORAGE (INITIAL 40960 NEXT 10240 MAXEXTENTS 110 PCTINCREASE 0) / CREATE UNIQUE INDEX PS_DEPT_EST_TBL_HM ON PS_DEPT_EST_TBL_HM (DEPTID, EFFDT DESC) TABLESPACE PSINDEX STORAGE (INITIAL 16384 NEXT 4096 MAXEXTENTS 110 PCTINCREASE 0) / CREATE INDEX PS#DEPT_EST_TBL_HM ON PS_DEPT_EST_TBL_HM (DEPTID, ESTABID) TABLESPACE PSINDEX STORAGE (INITIAL 10000 NEXT 100000 MAXEXTENTS 110 PCTINCREASE 0) / CREATE INDEX PS0DEPT_EST_TBL_HM ON PS_DEPT_EST_TBL_HM (ESTABID, DEPTID, EFFDT DESC) TABLESPACE PSINDEX STORAGE (INITIAL 10000 NEXT 100000 MAXEXTENTS 110 PCTINCREASE 0) / Hope that helps. Steve.