|
Notes |
|
|
|
|
As a new policy the failing tests will get a immediate priority. |
|
|
|
|
|
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
|
|
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 |
|
|
|
|
|
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
|
|
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
|
|
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 |
|