Greetings,
Hope everyone is having happy holidays to the extent that's relevant. I am
having a strange issue with a subclass of ERXBatchingDisplayGroup. I am
creating s search component to filter the results of the displayGroup.
I have created a qualifier, which appears correct. The SQL gene
I forgot to mention . . . The rows populated the displayGroup are from two
possible paths, so there are 55 total rows matching, of which 23 are distinct.
So we have a batching displayGroup with batches of 20, and the navigation
displays 3 pages for 55 matches, but the repetition which is populat
As a followup, I get the correct number of rows if I comment out any code which
sorts the displayGroup using attributes other than the id column of the entity
populating the displayGroup.
Without sorting, and with setUsesDistinct(true); I get 23 rows. Navigation
works.
If I then try to sort
On Dec 28, 2009, at 9:06 AM, Andrew R. Kinnie wrote:
As a followup, I get the correct number of rows if I comment out any
code which sorts the displayGroup using attributes other than the id
column of the entity populating the displayGroup.
Without sorting, and with setUsesDistinct(true);
OK, I have tried to generalize it, without changing anything significant.
Basically, the legacy architecture has a Student entity/table, a Person
entity/table (which represents Adults only, NOT students), a StudentPerson
entity/table which is essentially a join containing extra info not currentl
Also, the reason I point out the distinct/sorting issue is that the generated
SQL uses an order by in the outer select, and if you add distinct in the inner
select, it's not including the attributes required by the order by, but only
the id attribute. Thus, Oracle raises an error, because the d
And the qualifiers are what controls what SQL is generated. It could
also be the way the DG is combining the qualifiers internally. Maybe
try creating the OR externally and just setting one combined qualifier
on the DG. If that does not work, consider dropping the ERXKey stuff
and build
Thanks to Dave Avendasora, we have apparently fixed the issue by patching the
Oracle plugin to properly handle distinct and sorting in
ERXBatchingDisplayGroups.
He will file a jira with his patch.
Andrew
On Dec 28, 2009, at 3:06 PM, Chuck Hill wrote:
> And the qualifiers are what controls wh
http://issues.objectstyle.org/jira/browse/WONDER-439
It's a direct copy of the method used by Postgress and FrontBase's plugins.
I've tested it with our stuff and it seems to work perfectly.
Dave
On Dec 29, 2009, at 2:19 PM, Andrew R. Kinnie wrote:
> Thanks to Dave Avendasora, we have apparen
OK, we have narrowed this down dramatically.
We have a batching display group of objects from and Oracle DB.
We are grabbing objects from two separate paths, and therefore are using
distinct (setUsesDistinct(true);).
We are sorting the objects based on firstname then lastname (we have also tri
10 matches
Mail list logo
