I am reading a ton of docs about Magento’s API, Magento’s Models and Direct SQL calls. As I was reading that, the first conclusion is that direct sql calls would be very faster but I must take a special care at security, and the use of models make the development faster and easier but in the other hand, it loses performance manipulating huge catalogs.
I will have to deal with a shop with around 50k of products & heavy traffic, and I must export them to another server with category hierarchy, sku, description, image, product_name, url_path once and after it get only the updated ones once a hour. The best approach would be with direct sql calls, but will it be a suicide to make it with models? And do you think that integrate it with the SOAP API will be another suicide, and I should make it in a separate PHP to do this?
Super thanks in advance, I am very lost at this, and sorry for my bad English
Vinicius
There are many considerations here. I’m speaking about this because I have a similar issue. I’m currently using SQL to get the data from magento store to xml. Truely, using sql can make it faster ONLY if you know the attributes you’re fetching. eg. if your products have 15 attibutes, that means 50k x 15 attributes using sql. But at least you’ll be free from version issues because you’re using sql statements.
On the other hand…using models and API gives a lot of version issues especially if you’re developing for several magento versions. One other problem too is about magento custom attributes. Eg. If i add another attribute called ‘US SPECIAL SHIPPING’, It becomes quite difficult with the API.
If you don’t mind…you just make a direct sql call to all your attributes and save them to xml. That means you need very very fast machine to do this.
There is an extension on magento connect that serves comparison engines. It may fit your export neeeds. try it. price comparison script