Problem with retrieving RETS data

Question

I am working on one real estate site using the RETS service to retrieve data on my local server.

but I have one small problem, I can get data from RETS, which have about 3lacks of records in the RETS Database, but I did not find a way, How can I get that all records in a bunch of 50k at a time

I did not find the keyword “LIMIT” on RETS.so, how can I get “LIMIT” 50k at a time without records?

Please help me.

Answer 1

RETS is actually not very standard. This is more like a pseudo standard. It freely defines an XML schema that describes property listings.

In version 1.x, the “standard” consisted of DTD documents. In 2.x, the “standard” uses XSD documents to describe the list.

http://www.rets.org/documentation

However, in practice, there is practically no consistency between the performers. By connecting to hundreds of RETS Compliant service providers, I am convinced that none of them are like any other.

In addition, 2.x "standard" has not changed after 3 years. This is an unobtrusive, sloppy attempt at a standard. It (RETS) is often used as a word of business hype by non-technical people. This is actually just an arbitrary attempt to model real estate in XML.

Try asking a specific artist about your documentation. Often they do not have them. Thus, the email of the lead developer was often useful. Sometimes they will provide a WSDL that will describe the supported calls. Often WSDL does not match the actual service, so be careful.

For your specific question, try caching the results. Typically, using a RETS call restriction is a sign of a direct dependency. As service requests increase, the load that your service puts on itself will break (and not be evaluated). In addition, if their service decreases (even temporarily), yours will be interrupted. Most importantly, it will make the current requests to your pages really, really slow (especially if their system is slow at the time). Lists usually do not change often enough to worry about outdated data, so caching up to an hour is pretty acceptable.

Good luck

Answer 2

libRets provides support for generating queries with fetch restrictions:

http://www.crt.realtors.org/projects/rets/librets/documentation/api/classlibrets_1_1_search_request.html

But lately, I knew: I remember that Intereality either ignored it or did not directly provide full compatibility with RETS. The quickest way to find out how you deal with them is also the idea that the entire "System" name for the table fields is numerical.

If you're lucky, you are using a server running Rapattoni, and they provide a specification. compatible servers.

Last, I can't let my name remember my life, but I used the free Java-based RETS tool to create the right queries (including bias / restriction suggestions), and it made it a little easier to build automatic receivers for the client batch processing system.

Answer 3

In RETS, if Count More Than limit, we can download using the Batch form or we can delete this Limit using regex at boot

The best way to solve the problem is Divide the data into a small unit of loading, and for now we must take into account the restriction on loading. A field for splitting this in MLS / IDX. I suggest a modification date and listing.