Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0008900
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] A. Platformminorhave not tried2009-05-05 11:182011-09-07 13:36
ReportermtaalView Statuspublic 
Assigned Tomtaal 
PrioritynormalResolutionfixedFixed in Version3.0MP0
StatusclosedFix in branchFixed in SCM revision.
ProjectionnoneETAnoneTarget Versionpi
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionpiSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0008900: Inconsistencies between database default values and application dictionary default values

DescriptionApparently there is some lack of consistency in the default values. There are some columns that take default values at database level, but have no default value set at AP level. This makes causes some trouble when working with DAL, as some parameters need to be defined although it should be possible to leave them blank as they have a default value at database level. Example: qtyreserved in c_orderline. Database level: default=0. AP no default set.

A first step could be to add a test to check/validate the differences in default value setting between the database and application dictionary.
Tags250mp2
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]
related to defect 0009966 closedbalamurugan Boolean values of DB should be replaced by AD ones. 
related to defect 0009967 closedbalamurugan AD literals default values should not be quoted 
depends on defect 0009050pi closedmtaal Default value in database and application dictionary differ, they need to be the same 
depends on defect 0009051pi closedrafaroda Finance: Default value in database and application dictionary differ, they need to be the same 
depends on defect 0009052pi closedrafaroda MRP: Default value in database and application dictionary differ, they need to be the same 
depends on defect 0009053pi closedrafaroda Project: Default value in database and application dictionary differ, they need to be the same 
depends on defect 0009054pi closedrafaroda Common: Default value in database and application dictionary differ, they need to be the same 
related to defect 0008899 closedmtaal Column type in Application dictionary different to Database column type - UUID 
related to defect 0008897 closedAinhoaPagola Column type in Application dictionary different to Database column type - AD_Pinstance - UUID 

-  Notes
(0016122)
mtaal (manager)
2009-05-07 10:23

 Adding small remark from Antonio through email:
It is possible to get the default value for a column in dbsourcemanager, you just need to do column.getDefaultValue().
(0016392)
mtaal (manager)
2009-05-15 16:55

 I have implemented a check in the database.validation step. There were about 20 different differences, I have reported these as issues grouped by functional group. The check is disabled until all these issues have been solved otherwise it is not possible to reenable the check.

keeping this issue open until all the other newly reported issues have been solved.
(0018426)
rafaroda (developer)
2009-07-20 16:10

 Please notice that this differences should not be taken into account (false positives):
 -SYSDATE (in DB) and Sysdate (in AD) are logically identical (reference to
sytem date)
-'Y' (in DB) and Y (in AD) are logically identical (syntax in db requires
string literals to be quoted)
(0018435)
mtaal (manager)
2009-07-20 20:47

 The check should be adapted to specifically test for this case:
default value set in the DB, mandatory in AD, no default value in AD
(0040793)
mtaal (manager)
2011-09-07 13:36

 All child issues fixed
(0040795)
mtaal (manager)
2011-09-07 13:36

 All child issues fixed

- Issue History
Date Modified Username Field Change
2009-05-05 11:18 mtaal New Issue
2009-05-05 11:18 mtaal Assigned To => mtaal
2009-05-05 11:18 mtaal Regression testing => No
2009-05-05 11:20 mtaal Relationship added related to 0008899
2009-05-05 11:20 mtaal Relationship added related to 0008897
2009-05-05 12:03 psarobe Tag Attached: 250mp2
2009-05-05 12:04 psarobe Priority normal => urgent
2009-05-05 12:04 psarobe Status new => scheduled
2009-05-07 10:23 mtaal Note Added: 0016122
2009-05-15 16:52 mtaal Relationship added related to 0009050
2009-05-15 16:52 mtaal Relationship added depends on 0009051
2009-05-15 16:53 mtaal Relationship added related to 0009052
2009-05-15 16:53 mtaal Relationship added related to 0009053
2009-05-15 16:53 mtaal Relationship added related to 0009054
2009-05-15 16:55 mtaal Note Added: 0016392
2009-05-15 16:55 mtaal Relationship replaced depends on 0009050
2009-05-15 16:55 mtaal Relationship replaced depends on 0009052
2009-05-15 16:55 mtaal Relationship replaced depends on 0009053
2009-05-15 16:56 mtaal Relationship replaced depends on 0009054
2009-06-10 11:51 mtaal Priority urgent => normal
2009-07-20 15:56 rafaroda Severity major => minor
2009-07-20 15:56 rafaroda Relationship added related to 0009966
2009-07-20 16:05 rafaroda Relationship added related to 0009967
2009-07-20 16:10 rafaroda Note Added: 0018426
2009-07-20 20:47 mtaal Note Added: 0018435
2011-09-07 13:36 mtaal Note Added: 0040793
2011-09-07 13:36 mtaal Status scheduled => resolved
2011-09-07 13:36 mtaal Fixed in Version => 3.0MP0
2011-09-07 13:36 mtaal Fixed in SCM revision => .
2011-09-07 13:36 mtaal Resolution open => fixed
2011-09-07 13:36 mtaal Note Added: 0040795
2011-09-07 13:36 mtaal Status resolved => closed

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker