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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0008860
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] A. Platformmajoralways2009-05-01 13:492009-06-04 00:00
ReporterjpabloaeView Statuspublic 
Assigned Tomtaal 
PriorityimmediateResolutionno change requiredFixed in Version
StatusclosedFix in branchFixed in SCM revision.
ProjectionnoneETAnoneTarget Version
OSLinux 64 bitDatabasePostgreSQLJava version1.6.0_13
OS Version2.6.16Database version8.3.7Ant version1.7.1
Product VersionpiSCM revision2cd6c5bbdee5 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0008860: testSystemValidation junit test does not detect incosistencies in PostgreSQL

Descriptionorg.openbravo.test.system.SystemValidatorTest.testSystemValidation does not detect any database inconsistencies. On the same changeset and with Oracle issue 0008859 is raised.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to defect 0008859 closedmtaal C_TEMP_SELECTION and C_TEMP_SELECTION2 present in the database ant not in the AD 

-  Notes
(0016020)
jpabloae (reporter)
2009-05-04 17:52

As a new policy the failing tests will get a immediate priority.
(0016033)
shuehner (administrator)
2009-05-05 10:38

Note: this two tables are special. They are temporary tables. On oracle they do exist all the time but on postgres they are only created when used and do not exist outside the database session where they have been created.
(0016034)
mtaal (manager)
2009-05-05 10:44

Okay, this explains why the test fails on Oracle and passes on postgres.
There are two options:
1) add the table to the AD, this would however result in a failing test on postgres (and oracle will pass)
2) ignore this specific table in the test

I vote for 2)

gr. Martin
(0016035)
shuehner (administrator)
2009-05-05 10:59

Second option for this test looks good to me also. Question how do we check for compatibility for this tables? Or more generally compatibility for all manual small db-objects created in pre-script / post-script for postgres and oracle...
(0016037)
mtaal (manager)
2009-05-05 11:14

Hi Stefan,
Imo it is difficult to check for consistency of temporary db-objects. Do you know if there are many of those 'manual small' db-objects? Or what types are there?

gr. Martin
(0016056)
mtaal (manager)
2009-05-05 14:54

Closing this issue as it the solution will be handled in issue 8859. For the more general question on how to handle manual db-objects a new issue should be opened, or before we should discuss this topic by email/skype.

gr. Martin

- Issue History
Date Modified Username Field Change
2009-05-01 13:49 jpabloae New Issue
2009-05-01 13:49 jpabloae Assigned To => rafaroda
2009-05-01 13:49 jpabloae Regression testing => No
2009-05-04 17:52 jpabloae Note Added: 0016020
2009-05-04 17:52 jpabloae Priority urgent => immediate
2009-05-05 10:21 pjuvara Assigned To rafaroda => mtaal
2009-05-05 10:38 shuehner Note Added: 0016033
2009-05-05 10:44 mtaal Note Added: 0016034
2009-05-05 10:59 shuehner Note Added: 0016035
2009-05-05 11:14 mtaal Note Added: 0016037
2009-05-05 11:24 mtaal Relationship added related to 0008859
2009-05-05 12:01 psarobe Status new => scheduled
2009-05-05 12:01 psarobe fix_in_branch => pi
2009-05-05 14:54 mtaal Note Added: 0016056
2009-05-05 14:54 mtaal Status scheduled => resolved
2009-05-05 14:54 mtaal Resolution open => no change required
2009-05-05 14:54 mtaal Fixed in SCM revision => .
2009-05-05 14:54 mtaal fix_in_branch pi =>
2009-06-03 12:21 psarobe Status resolved => closed
2009-06-04 00:00 anonymous sf_bug_id 0 => 2800777


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker