[libRETS-users] Invalid Query Syntax
Keith T. Garner
kgarner at crt.realtors.org
Thu Dec 20 11:16:34 CST 2007
On 12/19/07 5:33 PM, Bill Linker wrote:
> I am trying to add in a way of excluding listings with XML parse
> errors…at least temporarily when waiting for the server to fix the
> error.
Mark and I are going to try to get a release out tomorrow that, among other
things, adds the ability to set a 'bigger' character set for the XML parser.
This should allow you to work around these problems in the future. The
default will be to stick to, more or less, ASCII, as that is what the RETS
1.x spec has as standard.
> It took them 5 or 6 days to fix the last error I found, so I
> would like to be able to just skip the bad listing(s) in the future.
> However, I am getting an ArgumentOutOfRangeException (C#) with the
> Message: “Invalid Query Syntax”.
You know, after I finish the new swig magic, I should go back and make some
of the exceptions match what they actually are better. We did a lazy swig
exception binding that seems to be mapping all exceptions to the same native
exception type.
In any case, you're getting that error from the server, as libRETS does no
processing of the DMQL you hand it.
> Here is the query:
> “(LISTSTATUS=|ACT),(LISTPRICE=400001-470000),(MLSNUM=~1234567)”
If I remember correctly, =~ is only valid for LOOKUPs, which TYPE in the
example you cited has to be. What you want to do is negate an existing
query, so you want something like "~(MLSNUM=1234567)"
Keith
--
Keith T. Garner - Managing Director - Center for REALTOR® Technology
kgarner at realtors.org - 312-329-3294 - http://blog.realtors.org/crt
More information about the libRETS-users
mailing list