Quick March 2010 update

First off, I did not make the initial commitment I promised myself which was to write one blog post every week so I’m going to take that back and just make blog posts when it is appropriate to do so. I think there is a world of difference in making blog posts for the sake of filling up space compared to talking about a specific issue.

Just a quick update on my progress. I have been busy doing commercial work for the past two months with various clients, one of which is helping Hermes Technologies to relaunch their web application, HiredHelp.ie , to make it suitable for deployment onto Heroku. One of the significant aspects of it is to redevelop their search capabilities to run on SOLR, rather than xapain as the former is supported by Heroku. That is still ongoing as we speak.

On another footnote, my own iphone application, S3 app has been officially launched and accepted by the app store. After several bug fixes and reviews the hard work has paid off and I was ecstatic to find out today that was the case. I want to thank the developers of ASIHTTP request library and Tapku library for the brilliant work they did on their open source projects, none of which this app will not have been what it is.

What’s next in the pipeline? I am working hard on pushing forward some of my own work which will be sold as products on the main site. One of which is a video encoding system and another a calendar application running on Redis DB, and it functions similarly to iCal but in the browser. Check this space for more details.

However back to the grind as they say!

Tagged with:
 

acts_as_xapian numeric range searching

I recently implemented Xapian and the acts_as_xapian plugin into my rails project. However, I ran into the ‘Unknown range’ operation error.

By applying the patches listed here and here, that solves the problem for me.

Please note that the changes have to be made to the ‘acts_as_xapian’ lib file within the vendors directory and then rebuild your index and restart your web app before seeing the changes take effect.

Also, if you are performing a numeric range search don’t prefix the values with ‘:’

For example, searching for ‘prices0..100′ is a numeric range search while ‘prices:low’ is a term search for specific attribute of that model.