Consultor Eletrônico



Kbase 18589: Unexpected Add Table behavior
Autor   Progress Software Corporation - Progress
Acesso   Público
Publicação   12/02/1999
Unexpected Add Table behavior

Unexpected Add Table behavior

Adding an area (specifying an area name) to a V8 df file "ADD TABLE"
entry prior to loading into V9 results in all subsequent tables to be
placed in the area defined for this "one" table.

All indexes continue to default to the "Schema Area" when
unassigned, as expected.
This behavior always occurs "after" the table entry change,
never before.
So that if the first table located in the data definitions file is
added to an area, all subsequent tables are added to this area.

Note that if a V9 df file is modified in this manner the same problem
occurs.

Example..
(Prior to loading data definitions)

ADD TABLE "Invoice"
AREA "Misc"
DESCRIPTION "The invoice table contains transactions for the
receivable module."
DUMP-NAME "invoice"
TABLE-TRIGGER "CREATE" NO-OVERRIDE PROCEDURE
"sports2000trgs/crinv.p" CRC "?"
TABLE-TRIGGER "DELETE" NO-OVERRIDE PROCEDURE
"sports2000trgs/delinv.p" CRC "?"

ADD TABLE "Customer"
DESCRIPTION "The customer table contains customer information
including balance and address."
DUMP-NAME "customer"
TABLE-TRIGGER "CREATE" NO-OVERRIDE PROCEDURE
"sports2000trgs/crcust.p" CRC "?"
TABLE-TRIGGER "DELETE" NO-OVERRIDE PROCEDURE
"sports2000trgs/delcust.p" CRC "?"


(After Dumping data definitions)

ADD TABLE "Invoice"
AREA "Misc"
DESCRIPTION "The invoice table contains transactions for the
receivable module."
DUMP-NAME "invoice"
TABLE-TRIGGER "CREATE" NO-OVERRIDE PROCEDURE
"sports2000trgs/crinv.p" CRC "?"
TABLE-TRIGGER "DELETE" NO-OVERRIDE PROCEDURE
"sports2000trgs/delinv.p" CRC "?"

ADD TABLE "Customer"
AREA "Misc"
DESCRIPTION "The customer table contains customer information
including balance and address."
DUMP-NAME "customer"
TABLE-TRIGGER "CREATE" NO-OVERRIDE PROCEDURE
"sports2000trgs/crcust.p" CRC "?"
TABLE-TRIGGER "DELETE" NO-OVERRIDE PROCEDURE
"sports2000trgs/delcust.p" CRC "?"


EXPECTED RESULTS: Expected behavior is that any tables not area define
d
should default to the schema area.

DISCLAIMER


The origins of this information may be internal or external to
Progress Software Corporation. Progress Software Corporation makes
all reasonable efforts to verify this information. However, the
information provided in this document is for your information only.
Progress Software Corporation makes no explicit or implied claims to
the validity of this information.

Any trademarks referenced in this document are the property of their
respective owners. Consult your product manuals for complete
trademark information.

Copyright 1998 Progress Software Corporation, Inc.
All Rights Reserved.