Openbravo Issue Tracking System - Openbravo ERP | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0007306 | Openbravo ERP | A. Platform | public | 2009-02-02 10:03 | 2009-03-06 12:34 |
| Reporter | mtaal | ||||
| Assigned To | mtaal | ||||
| Priority | normal | Severity | major | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | pi | ||||
| Target Version | pi | Fixed in Version | |||
| Merge Request Status | |||||
| Review Assigned To | |||||
| OBNetwork customer | |||||
| Web browser | |||||
| Modules | Core | ||||
| Support ticket | |||||
| Regression level | |||||
| Regression date | |||||
| Regression introduced in release | |||||
| Regression introduced by commit | |||||
| Triggers an Emergency Pack | No | ||||
| Summary | 0007306: Solve various validation errors reported by the validate.database task | ||||
| Description | The reported validation errors with the change which needs to be made: c.- Table C_TEMP_SELECTION and C_TEMP_SELECTION2 present in the database but not defined in the Application Dictionary -> MTA should change the validation to not take into account "TEMPORARY" tables when reading db tables. Both tables are not in our standard model but generated in the prescript. Temporary tables will never be part of our model (dbSourceManager will never create a temporary table from the model). DB dictionary tables (USER_TABLES) have a isTemporary column ("TEMPORARY" in oracle) d.- Mandatory but nullable columns: I would disable this validation in 2.50. To properly manage this case we need to implement the "mandatory" attribute in fields. In 2.60 there is a clean-up project planned that should enable back this validation and include a review on this columns. -> MTA should send an email to Stefan -who will lead the cleanup- to put this as a feature request for the cleanup project. You should explain to him the validation process because for sure Stefan will extend it with new rules during the clean-up e.- Not nullable but not mandatory columns -> MTA should set all of them as mandatory in AD (automatic script) f.- Wrong type: mistakes with lists -> MTA should change the validation for lists, it should be VARCHAR(60). In my last email I said that datatype in lists should be VARCHAR2(60) but it is the sub-type in oracle (sorry, my fault). VARCHAR2 in oracle is equivalent to VARCHAR in postgresql and the type in our model is VARCHAR (afaic you are using DBSourceManager to read the model from db). Oracle has VARCHAR2 and NVARCHAR2 and not VARCHAR AND NVARCHAR (strange naming in oracle due to historical reasons). g.- Wrong type: mistakes with USER1_ID, USER2_ID -> MTA should change the ad_reference_id of these columns to 10 (string) and ad_referencevalue_id to null (these columns are supposed to be used as foreing keys to user defined dimensions, so they should be tableDir or tableReference or search, but since the referenced entity does not exist is is better to put them as string) | ||||
| Steps To Reproduce | |||||
| Proposed Solution | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2009-02-02 10:03 | mtaal | New Issue | |||
| 2009-02-02 10:03 | mtaal | Assigned To | => mtaal | ||
| 2009-02-02 10:03 | mtaal | sf_bug_id | 0 => 2556395 | ||
| 2009-02-02 10:03 | mtaal | Regression testing | => No | ||
| 2009-02-03 10:52 | psarobe | Status | new => scheduled | ||
| 2009-02-03 10:52 | psarobe | fix_in_branch | => trunk | ||
| 2009-02-04 14:56 | svnbot | Checkin | |||
| 2009-02-04 14:56 | svnbot | Note Added: 0013143 | |||
| 2009-02-04 14:56 | svnbot | Status | scheduled => resolved | ||
| 2009-02-04 14:56 | svnbot | Resolution | open => fixed | ||
| 2009-02-04 14:56 | svnbot | svn_revision | => 12775 | ||
| 2009-03-06 12:34 | psarobe | Status | resolved => closed | ||
| Notes | |||||
|
|
|||||
|
|
||||