Project: 	
  | View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0031336 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| defect | [Openbravo ERP] 02. Master data management | minor | have not tried | 2015-11-03 13:36 | 2015-11-03 13:36 | |||||||
| Reporter | AugustoMauch | View Status | public | |||||||||
| Assigned To | Triage Omni OMS | |||||||||||
| Priority | normal | Resolution | open | Fixed in Version | ||||||||
| Status | new | Fix in branch | Fixed in SCM revision | |||||||||
| Projection | none | ETA | none | Target Version | ||||||||
| OS | Any | Database | Any | Java version | ||||||||
| OS Version | Database version | Ant version | ||||||||||
| Product Version | SCM revision | |||||||||||
| Merge Request Status | ||||||||||||
| Review Assigned To | ||||||||||||
| OBNetwork customer | No | |||||||||||
| Web browser | ||||||||||||
| Modules | Core | |||||||||||
| Support ticket | ||||||||||||
| Regression level | ||||||||||||
| Regression date | ||||||||||||
| Regression introduced in release | ||||||||||||
| Regression introduced by commit | ||||||||||||
| Triggers an Emergency Pack | No | |||||||||||
| Summary | 0031336: The c_reject_reason table should be included in the Client Definition dataset | |||||||||||
| Description | The c_reject_reason_id column of the c_order table references the c_reject_reason table.  The problem is that the c_order table is included in the Client Definition dataset, but the c_reject_reason table is not. This will cause referencial integrity problems when importing a sample data that containes not null values in the c_reject_reason_id column of the c_reject_reason table.  | |||||||||||
| Steps To Reproduce | For any client: - Add values to some rows in the c_reject_reason_id column of the c_order table. - export the sample data for that client: ant export.sample.data -Dclient="YourClient" -Dmodule=org.openbravo this will generate a XML file for the c_order that contains values for its c_reject_reason_id column, but it will not generate a XML file for the c_reject_reason table - Import the sample data for that client, for instance by executing ant install.source. There will be referencial integrity problemes like these: [java] 161567 WARN - SQL Command failed with: ERROR: insert or update on table "c_order" violates foreign key constraint "c_order_reject_reason" [java] Detail: Key (c_reject_reason_id)=(1F4B6B9432EA9A5055D8ECD6552BFD05) is not present in table "c_reject_reason".  | |||||||||||
| Tags | No tags attached. | |||||||||||
| Attached Files | ||||||||||||
		  Relationships		[ Relation Graph ] 
		[ Dependency Graph ] 
			 | 
|
  Issue History	 | 
|||
| Date Modified | Username | Field | Change | 
| 2015-11-03 13:36 | AugustoMauch | New Issue | |
| 2015-11-03 13:36 | AugustoMauch | Assigned To | => Triage Finance | 
| 2015-11-03 13:36 | AugustoMauch | OBNetwork customer | => No | 
| 2015-11-03 13:36 | AugustoMauch | Modules | => Core | 
| 2015-11-03 13:36 | AugustoMauch | Triggers an Emergency Pack | => No | 
| Copyright © 2000 - 2009 MantisBT Group |