So I nagged Novell to add a config option to enable Query-ex in the SOAP
driver and it is there in the latest patch. Yay!

So I try to do a query for a Migrate from Application, using an XDS doc
I send in via dxcmd that looks like this:

<nds dtdversion="3.5" ndsversion="8.x">
<source>
<product version="3.6.10.4747">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<input>
<query class-name="List" scope="subtree">
<search-class class-name="List"/>
<read-attr attr-name="Full Name"/>
</query>
</input>
</nds>

This is important, as with no <read-attr> nodes the query is assumed to
be all attributes and in this system, there is a penalty for more
attributes in terms of processing time. (as much as 20 minute penalty
seen so far).

But the engine sees a Migrate query command, sees it supports Query-ex,
and converts it, which is actually good!

So we this in trace:
[08/30/10 11:55:46.912]:sfdc ST:Subscriber processing query for .
[08/30/10 11:55:46.912]:sfdc ST:Querying application for objects to migrate.
[08/30/10 11:55:46.912]:sfdc ST:Converting <query> to <query-ex>
[08/30/10 11:55:46.912]:sfdc ST:Fixing up association references.
[08/30/10 11:55:46.914]:sfdc ST:
<nds dtdversion="3.5" ndsversion="8.x">
<source>
<product version="3.6.10.4747">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<input>
<query-ex class-name="User_Signature__c" event-id="0"
max-result-count="2000" scope="subtree">
<search-class class-name="User_Signature__c"/>

<read-attr/>
</query-ex>
</input>
</nds>

You can see that my <read-attr attr-name="Full Name"/> line got changed
to <read-attr/> which is a bit annoying. Also, there is that extra
blank line, which I did not add, it is really there in trace as well.

So is this a bug, or WAD?

I can solve this for my basic issue by using the fact I wrote a way to
send direct SOQL queries to my connected system, but that does not
obviate the issue.