ActiveRecord::Base class_name weirdness
Reported by Eadz | June 10th, 2008 @ 03:51 AM
class_name should return the class name or be called something else.
## Rails IRB Session, Rails 2.1
class DummyOne < ActiveRecord::Base
end
>> DummyOne.class_name
=> "DummyOne"
class DummyTwo < ActiveRecord::Base
set_table_name "dt"
end
>> DummyTwo.class_name
=> "Dt" ##
Comments and changes to this ticket
-
Cheah Chu Yeow June 23rd, 2008 @ 04:32 PM
Hmm, you can actually simply use Module#name:
DummyTwo.nameAR::Base#class_name is actually documented like so:
"Turns the +table_name+ back into a class name following the reverse rules of +table_name+."
So while the method name may be misleading, I don't think it was intended to be used the way you described.
-
Eadz June 27th, 2008 @ 01:09 AM
- → Tag changed from “” to “activerecord tiny”
In the context of "Turns the +table_name+ back into a class name" what exactly is a "class name" if not the name of the class?
-
Tarmo Tänav September 18th, 2008 @ 08:02 AM
- → Tag changed from “activerecord tiny” to “activerecord tiny”
Perhaps the method should be removed?, nothing in AR seems to depend on it (the only test that breaks when this method is broken is the test for this method) and as is clear from this ticket it is misleading and, at least to me, seems practically useless.
-
Pratik December 19th, 2008 @ 03:49 PM
- → State changed from “new” to “incomplete”
- → Assigned user changed from “” to “Tarmo Tänav”
Need to deprecate the method too. Patch/Commit please :)
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
Repository is at http://github.com/rails/rails
Check out the development master (Edge Rails):
git clone git://github.com/rails/rails.git
Creating or reviewing a patch
See the contributor guide.
Creating a feature request
Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too"..
Tom Ward