[Rets-dev] Problem with Importing Rets (MRMLS) listings

Tue Apr 10 07:35:46 CDT 2007

ive only ever run into one vendor that provides no means to pull the
entirety of a query, no matter the query.   this means that you likely have
one of two options:

1) try forcing the limit to none
2) try paging with the offset/limit

in the unfortunate event that you are also querying a vendor that doesnt
support returning a complete a dataset,  you'll have to fudge it with your
own paging mechanism.   this could be by segmenting your queries by some
general criteria, but this can often be tricky as you have no guarantees
where those size boundaries are.

another option is to directly implementing paging on a field that can gives
a solid binary splitting option.  like a date field that is non-volatile,
evenly distributed and non-null (as that would lump an unsegmentable set of
values together).  if you find a date, like entry date or something, you
should be able to do the trick with that.   the idea is, prior to pulling
your query, do a count.  if the count is too large, split it in two (the
first split is arbitrary), recurse.

hope this helps,
jp

On 4/10/07, Sangeeta Arora - CIPL <sangeeta at classicinformatics.com> wrote:
>
> Hi Paul,
>
> Yes, I am getting <MAXROWS/> tag in the last of the data. When I am
> getting
> <MAXROWS/> tag then it returns only 5000 rows (listings).
>
> Is this the problem? It means that if I am not getting <MAXROWS/> tag then
> MRMLS returns complete listing. Is this true?
>
> Regards,
>
> Sangeeta Arora
>
> -----Original Message-----
> From: Paul Stusiak [mailto:pstusiak at falcontechnologies.com]
> Sent: Tuesday, April 10, 2007 12:24 PM
> To: Sangeeta Arora - CIPL
> Cc: rets-dev at rets.org
> Subject: Re: [Rets-dev] Problem with Importing Rets (MRMLS) listings
>
> Most systems do not permit unqualified queries - large row sets. Some
> vendors have implemented the optional RETS parameters of offset while
> others have different methods for pulling such data. Some do not allow
> such types of queries, either for technical reasons or for policy
> reasons. Some systems will deny access to connections that do "nasty"
> requests, those requests that make an unreasonable demand on the system
> or limit such queries to a specific time window.
>
> You should contact MRMLS to determine what is permitted and how they
> suggest formulating the query for optimum accuracy and performance. I
> suspect that they will provide you with a technique to walk the results
> through multiple requests. On some systems, if it were permitted, your
> request may result in more than 500,000 rows.
>
> In any case, you should be seeing the <MAXROWS/> tag if you have
> additional records that can't be sent. You didn't say that you were
> getting a 20208 response.
>
> Again, I believe that you need to contact the MLS directly.
>
> Paul
>
> Sangeeta Arora - CIPL wrote:
> > Hi Paul,
> >
> > I am connecting with the production server. I am also getting the active
> > listings. My problem is that when I am importing the properties then it
> is
> > not giving the complete list of properties. It gives the old properties
> not
> > the new one. I think, it exceeds the maximum limit to return the
> listings.
>
> >
> > I am using this query.
> >
> >
>
> $query="CLASS=listing_mrmls_$propType&searchtype=Property&querytype=DMQL2&Qu
> > ery=(state=ca)&StandardNames=0&Format=Standard-XML:1.0";
> >
> > Here, I am importing the properties for MRMLS for CA state and $propType
> > means RESI, RINC etc. It returns me XML.
> >
> > Thanks,
> >
> > San
> >
> > -----Original Message-----
> > From: Paul Stusiak [mailto:pstusiak at falcontechnologies.com]
> > Sent: Tuesday, April 10, 2007 11:25 AM
> > To: Sangeeta Arora - CIPL
> > Cc: rets-dev at rets.org
> > Subject: Re: [Rets-dev] Problem with Importing Rets (MRMLS) listings
> >
> > I'd suggest that you get in contact with MRMLS to determine the best way
> > to generate queries of the type you need.
> >
> > Failing that, I'd suggest you contact the vendor.
> >
> > This list is generally used for questions about RETS and less about
> > questions on specific vendor implementations, although helpful people
> > may answer your questions.
> >
> > The MLS should be able to get you an implementation guide, direct you to
> > the correct resource or get you in contact with the appropriate
> > resources at the vendor.
> >
> > As a general observation, your question is not very specific. There are
> > several questions that you should get answered when you speak with the
> MLS.
> >     1. does your access permit you to see the active listings?
> >     2. does the system permit unlimited row-sets (unlikely) and if not,
> > how do you get the information you need?
> >     3. what is the correct field name for the modification timestamp (to
> > get new listings rather than attempting to get them all again and again
> > when nothing has changed)?
> >     4. are you using the correct class and type to get the information?
> > Maybe you are looking at the historical information.
> >     5. are you connecting to a test server or the production server? Not
> > all test servers have listings that look "real".
> >
> > Failing that, you could use something like Conduit to get some listings
> > and observe what that application does to retrieve them.
> >
> > Paul
> >
> > Sangeeta Arora - CIPL wrote:
> >
> >> Hi,
> >>
> >> I am San. I am importing the Rets (MRMLS) properties. But I am getting
> >>
> > only
> >
> >> the old ones. Can you please suggest me that how I can import the new
> ones
> >> and all the listings? I am importing it through
> >> http://rets2.mrmlsmatrix.com.
> >>
> >> Please help me, if you can. It's really urgent for me.
> >>
> >> Thanks,
> >>
> >> San
> >>
> >>
> >>
> >> _______________________________________________
> >> Rets-dev mailing list
> >> Rets-dev at rets.org
> >> http://lists.rets.org/mailman/listinfo/rets-dev
> >>
> >>
> >>
> >>
> >
> >
>
> --
> Paul Stusiak
> Falcon Technologies Corp.
>
>
>
>
>
> _______________________________________________
> Rets-dev mailing list
> Rets-dev at rets.org
> http://lists.rets.org/mailman/listinfo/rets-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rets.org/pipermail/rets-dev/attachments/20070410/66ee29c4/attachment.html