[libRETS-users] SQL-Like Querying Rets db
Agustin Garzon
agustingarzon at yahoo.com
Tue Jul 3 16:51:46 CDT 2007
Keith, as you said, MLNumber is not the StandardName.
It's ListingId instead!
So, I performed the same query, with StandartNames enabled, used the right names, and got the results.
But I've got less columns in the SearchResultSet.
All the Tables (for what I can observe) without a StandardName in the Metadata, is absent in the result set.
In the server I'm dealing with there are dozens of tables with no standard name.
It's not a problem for me, it's just something I noticed, data could be lost, so I'll stick to Matt's suggestion, USE THE SHORT NAMES!
-----
Having such a prompt support from you people is tempting to stop researching!
It would be great having a search feature on the Librets User List web site.
With best regards,
Agustin Garzon
----- Original Message ----
From: Keith T. Garner <kgarner at crt.realtors.org>
To: For discussion and help for and by the users of the libRETS C++ library <librets-users at crt.realtors.org>
Sent: Tuesday, July 3, 2007 5:05:24 PM
Subject: Re: [libRETS-users] SQL-Like Querying Rets db
On 7/3/07 2:41 PM, Agustin Garzon wrote:
> Hey there!
>
> I've noticed something interesting regarding this topic.
> If I don't disable StandardNames, as recommended by Mark and Keith, and
> I feed the StandardName "ResidentialProperty" (see metadata below) to
> the Class part in the query, I got an error stating:
> "The query Could not be executed because supplied login doesn't have
> access to the MLNumber field"
> Why the heck ?
That's probably because MLNumber doesn't exist in StandardNames mode.
MLNumber is probably the SystemName. It probably has a different StandardName.
> Anyway, if I disable StandardNames, then everything seems to work fine.
> THANKS MATT! THANKS KEITH!
No problem.
> Finally, I would like to contribute recommending you to name the
> SearchRequest parameters in a way to visually identify if it's referring
> the ClassName or the StandardName.
> SearchRequest(string ResourceID, string ClassName, string Query);
I guess I'm not understanding what you're asking here. The name could/would
be wrong depending on how you SetStandardNames.
As it is, the current naming in consistant with the RETS spec and the
terminology it uses within it for the Search operation. I'd rather not move
away from that.
Keith
--
Keith T. Garner - Managing Director - Center for REALTOR® Technology
kgarner at realtors.org - 312-329-3294 - http://blog.realtors.org/crt
_______________________________________________
libRETS-users mailing list
libRETS-users at crt.realtors.org
http://mail.crt.realtors.org/mailman/listinfo/librets-users
____________________________________________________________________________________
Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out.
http://answers.yahoo.com/dir/?link=list&sid=396545433
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.crt.realtors.org/pipermail/librets-users/attachments/20070703/2113ad75/attachment.html
More information about the libRETS-users
mailing list