How to Apply VO Where Clause to New Rows

In this article I describe the solution we found for a problem with Subtype VO's. We had 2 ADF BC View Objects, each representing a different subtype of the database table without extending a supertype VO. The problem was: new rows appeared in the set of both View Objects, even though each new row clearly belonged to only one of the subtypes. The solution is to use the ADF BC RowMatch or RowQualifier to apply in-memory filtering.

If you read the example solution carefully, you will see that the RowMatch applied does not correspond completely to the where clause of that View Object. That is because expressions like "is null" or "is not null" cannot be used in RowMatches. The expression "is not null" can for Number attributes be replaced by something like "Attribute > 0", but I have not found a solution for "is null" yet. If you have a suggestion, please leave a Comment on this post!

Comments:

Maybe this problem can be solved by adding a transient attribute CommissionIsNull which returns "true" or "false", and then checking for CommissionIsNull = 'true'.

Posted by Sandra Muller on November 19, 2007 at 06:53 PM PST #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Java EE Consultants - JHeadstart, ADF, JSF

Search

Archives
« July 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
  
       
Today