[PATCH] Class-table inheritance for ActiveRecord

Anything happening with this?

Sadly I have not had time to work on this. I've been way too busy at work so had to resort to STI. I've not been following the ActiveRecord code but I know from a post on our blog that the patch no longer works. Not sure how much work it would take to get it back up and working - after that it just needs fixing for associations.

Were you interested in working on it donv?

Yes, I would be interrested in working on this. I have 27 years of experience coding, 3 of them with ruby, and 2 of them with Rails. I am mostly interested in getting my own cases to work, but can contribute to a complete solution if properly motivated :)

I have been using a simple ClTI implementation published at

http://wiki.rubyonrails.com/rails/pages/ClassTableInheritanceInRails

which is OK, and could be developed further. It is only 85 lines (no tests), and is installed as one required file, and even supports associations. You may want to look at it and include a reference link from your page to that page.

I like your implementation better since it has simpler usage and avoids the 'type' column. Also your test suite gives confidence.

Do you think it will ever be included in Rails Core? Otherwise it should be packaged as a gem or plugin.

I am currently using EdgeRails revision 6747 on the project I am using ClTI with. I assume this will cause trouble?

Is your code in any available repository? Maybe RubyForge?

Cool I was hoping someone would take it over.

I've met the guy that wrote that patch although I hadn't actually seen that code before. (When I get round to cleaning up the blog I will link to it.) He told me he didn't end up using it much because he didn't have time to support issues other developers had with it. That's one of the big problems implementing CTI, I found - making it seamless in every situation is quite tough. My version gets right into the core loading code which is why the patch is so much longer.

I would like to think this would make it into core at some time. CTI is a killer feature for any ORM library IMHO. You will not be able to apply the patch immediately to a recent edge rails - you are best checking out the revision the patch applies to and updating, and seeing where it breaks.

The code is not in a repository, only here. Since it is a patch against the ActiveRecord code there is no real code to move into a repository. If it is possible to make this work as a plugin that would be great, but since it hacks so much of the core code it might not be easy.

WDYT?

What revision does the patch apply to?

Leading the project would be to much for me, if that is what you meant by "take it over". Using, testing, and contributing code is what I am looking for :)

I am sure many others would like to contribute to this project, given the chance.

Can't remember what revision it applies to - check the patch file, it's somewhere in the header

I never thought of this as a "project", more of a "hack" or a "patch". To do this collaboratively, we would ideally need a branch in the rails repository, although I guess it could be done by importing into a new repository hosted elsewhere.

Any ideas how best to ressurect this? I spent a solid month on it, so it would be nice to think it won't go to waste.