[Rets-dev] Behaviour when a table is asked for twice

[Keith T. Garner]

A and B are the exact same conclusions I came to before sending my e-mail.
I hadn't even considered C.  I had asked the group just in case there was an
angle I hadn't though of.  Thanks for mentioning C, Libor.

I agree, a server should do A or B.

Keith

Libor Viktorin wrote:
> By my opinion, the server has several options:
> A) It may see the second MLNumber as different from the first, in which
> case it's an unknown field. Then the server may either refuse the query
> and return an error, or ignore it and return less fields.
> B) It may see both MLNumbers as referring to the same field, in which
> case it should return just one MLNumber. In other words, it returns just
> the fields mentioned in the SELECT argument, and does not return any
> fields that are not there.
> C) It may see the MLNumber requests as request to return two instances
> of the same data. In compact format, it would return two identical
> columns. In Standard-XML, I am afraid the DTD does not allow for
> multiple copies of the same field, so this is not a real option and the
> server should choose between A) and B).
> 
> Returning a field whose name is not in the metadata and in the DTD is
> definitely wrong.
> 
> Libor



-- 
   Keith T. Garner - Strategic Architect - Center for REALTOR® Technology
     kgarner at realtors.org - 312-329-3294 - http://blog.realtors.org/crt