Confounding URL typists since 2007.
Rails 3.1.0 has dropped, and hours later I received my first “report” that MetaWhere doesn’t work with Rails 3.1. For those of you who read this blog or , this should come as no surprise. Still, I wanted to make a quick announcement here, if only to have a place to link people to when they inquire.
Read the rest of this post
Not too long ago, I mentioned that a rename for MetaWhere 2.0 was coming. It’s here, and the new name is Squeel. A lot has happened since my post about the rewrite a couple months ago, but before we get into that, a bit about the name…
Read the rest of this post
A couple of nights ago, I pushed Ransack to GitHub. What’s Ransack? Well, previously I was calling it MetaSearch 2.0, and it’s a complete rewrite, not unlike the MetaWhere 2.0 development in the rewrite branch (a name change is also forthcoming for MW 2.0, if you’re curious). Why change names? A few reasons:
Read the rest of this post
If you or have been following the rails core mailing list lately, you might have seen mention of the MetaWhere rewrite I’ve been working on. If you haven’t, let me start by linking you to the rewrite branch on GitHub. This is just a quick post explaining why I’m rewriting it, and why you should care.
This has been a long time coming. Both MetaSearch and MetaWhere entered development as Rails 3-only gems early last year. Developing them was a great learning process, as I got to dive deeper into the innards of Rails and ARel than I ever expected, and track ARel through a complete rewrite and maintainer change, as well. The only updates you’ll notice from the last released gems are the docs (MetaSearch/MetaWhere), which should now be up to date (site docs to follow soon). It feels good to finally hit 1.0!
Things have largely quieted down on the MetaSearch/MetaWhere front. The currently released gems are working well for me on a few large-ish projects, and I haven’t seen any serious bug reports in quite some time. I’m happy with the existing APIs, and while I’d certainly like to do a bit of refactoring, that’s nothing that should result in a breaking change. All this being said, I’m considering the latest releases of MW/MS as release candidates, and will be pushing out 1.0.0 of both relatively soon, barring any serious issues. Please get your bug reports in now!
The next release of MetaWhere is shaping up to add a couple of cool new features to ActiveRecord — control over join type, and access to SQL functions supported by your database. Before I go into details about them, I’d like to ask those of you who are testing Rails 3-0-stable branch and ARel master already to try out the arel-2.0 branch, where these fun changes live. I’d appreciate feedback on how well they work for your apps. Now, on with the show. Read the rest of this post
So, the Rails team released Rails 3.0 yesterday, on my birthday. I am claiming it as my birthday present. Anyway, I ran a quick test on MetaWhere and MetaSearch and everything is still passing, so we should be good to go! Let me know if it’s not the case.
If you updated MetaWhere recently, and your application started raising MetaWhereInAssociationErrors, I’m sorry. But not too sorry. Because that error probably saved you from running into strange, confusing problems later. Let me explain.
Read the rest of this post
With Rails 3.0 RC released, I decided I’d better step up the pace on the promise I made to cover recent updates to MetaWhere and MetaSearch in more detail prior to Rails 3 final. Tonight, I’d like to spend some time on detailing the changes to MetaWhere since 0.3.3.
Read the rest of this post