Anonymous | Login | Signup for a new account | 2024-05-19 09:00 CDT |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Dependency Graph | [ View Issue ] [ Relation Graph ] [ Vertical ] | |||
|
||||
|
Viewing Issue Simple Details | |||||
ID | Category | Type | Reproducibility | Date Submitted | Last Update |
0000489 | [In-Portal CMS] Data Management | feature request | N/A | 2009-12-23 04:28 | 2009-12-23 04:30 |
Reporter | alex | View Status | public | ||
Assigned To | |||||
Priority | normal | Resolution | open | ||
Status | active | ||||
Summary | 0000489: Protection against related record deletion in grids | ||||
Description |
There are two type of database record relations in In-Portal: * direct - related record is subitem of main record (relation is defined in unit config); * indirect - there is dropdown in one table, where you can select data from other table (no direct relation defined on unit config level). When main record is deleted, then subitems are deleted as well, so it's not a problem (this is direct relation). For indirect relation this creates a problem. I propose to define field relations with other tables in unit config. Such relation will be used to check for related data before actual database record is deleted. This feature will preserve data integrity. Here is proposed data format (in main unit config, which shows data from other unit configs): 'DependentFields' => Array ( 'MainFieldA' => 'related-prefixA_FieldNameA', 'MainFieldB' => 'related-prefixB_FieldNameB', ); For example you can delete payment type, that is used in orders. |
||||
Additional Information |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Web Development by Intechnic In-Portal Open Source CMS |