+1. I agree.
I guess I was trying to come up with a solution that preserves as many
common things perfromed by DataNode. DataNode's functionality is melting
down, as a result of pushing more and more stuff into adapter. Eventually
(not now) DataNode and adapter will likely become the same thing, which is
probably a good thing.
Andrus
> Just a thought. Maybe DataNode should let an instance of QueryRunner to
> retrieve QueryTranslator internally from its native DbAdapter so we
> would hide all the details of translation and execution in QueryRunner.
> Something like:
> public abstract void run{query type}(
> DataNode node,
> {query type}Query query,
> OperationObserver delegate)
> throws Exception;
>
>
>>
>> 1. Ask adapter to create QueryTranslator
>> 2. Ask adapter to create QueryRunner
>> 3. Determine what method to invoke on the runner based on query type
>> 4. Invoke this method on the runner.
>>
>> Any thoughts?
>>
>> Andrus
This archive was generated by hypermail 2.0.0 : Fri Mar 14 2003 - 10:33:01 EST