Andrea Aime wrote:
> Hum,
> first off, I don't see why rendering should be dealing with paging.
I assume it is so people can see on the map what rows they are looking
at in a table?
But yes I was close; it looks like I have tracked the problem down to
DataUtilities.createSubType not handling the
I had come to this conclusion myself; my concern is paging being handled
differently at different points (even within streaming renderer there
are several calls to mixQueries).
But I agree; paging does not really work when combining queries (at
least not in any efficient manner).
Jody
Andrea A
Jody Garnett ha scritto:
> Jody Garnett wrote:
>> I am going through the code in streaming renderer; trying to see why
>> uDig is having trouble rendering features.
>>
>> Streaming renderer traditionally delegates the task of combining two
>> queries to DataUtilities.mixQueries method; when I rev
Jody Garnett ha scritto:
> I am going through the code in streaming renderer; trying to see why
> uDig is having trouble rendering features.
>
> Streaming renderer traditionally delegates the task of combining two
> queries to DataUtilities.mixQueries method; when I review the code today
> I fi
Jody Garnett wrote:
> I am going through the code in streaming renderer; trying to see why
> uDig is having trouble rendering features.
>
> Streaming renderer traditionally delegates the task of combining two
> queries to DataUtilities.mixQueries method; when I review the code today
> I find tha
I am going through the code in streaming renderer; trying to see why
uDig is having trouble rendering features.
Streaming renderer traditionally delegates the task of combining two
queries to DataUtilities.mixQueries method; when I review the code today
I find that startIndex is only handled a
