[libRETS-users] Strange Error

[Russ Perna]

Keith,

I had actually tried both way, and neither seems to work.

Thanks,
Russ 


Russ Perna
--
Senior Developer
Prudential Rand Realty
http://www.prudentialrand.com
845.825.8036
 
 

-----Original Message-----
From: librets-users-bounces at crt.realtors.org
[mailto:librets-users-bounces at crt.realtors.org] On Behalf Of Keith T. Garner
Sent: Wednesday, December 19, 2007 1:16 PM
To: For discussion and help for and by the users of the libRETS C++ library
Subject: Re: [libRETS-users] Strange Error


On 12/19/07 12:06 PM, Russ Perna wrote:
> Maybe it could be something else then.
> 
> This is the request from RETS Connector:
> URI:
> /Search.asmx/Search?SearchType=Property&Class=1&Select=217&Format=COMP
> ACT&Qu
> eryType=DMQL2&Query=(290=%7CACT),(40=%7C440)
> 
> This is the request from libRets:
> URI:
> /Search.asmx/Search?Class=1&Count=1&Format=COMPACT&Query=(290%3dACT),(
> 40%3d4 
> 40)&QueryType=DMQL2&SearchType=Property&Select=217&StandardNames=0
> 
> Does this tell you anything that I might be missing?

Yes, you are not querying the LOOKUPs with the syntax for querying LOOKUPs.

Your query is "(290=ACT),(40=440)" when it should be "(290=|ACT),(40=|440)"
 In your example from RETSConnector, you can see a %7C in their URLEncoded
version.  %7C is | when decoded.

kgarner at copper [501]:irb
irb(main):001:0> require 'uri'

irb(main):003:0> URI.unescape('(290=%7CACT),(40=%7C440)')
=> "(290=|ACT),(40=|440)"


The RETS metadata is your friend.  Both of those tables should tell you that
their interpretation is LOOKUP.

Keith

--
  Keith T. Garner - Managing Director - Center for REALTORR 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