CompanyBook/massive_record — Issue #83: Inheritance and table_name
Author: corywilkerson
Created: 2011-12-30 21:34:39+00:00
State: open

Maybe I'm missing something obvious but I'm noticing that I can't explicitly set table name (using set_table_name) when I've inherited from a superclass.

For instance:

```ruby
class Foo < MassiveRecord::ORM::Table
default_scope select(:d)

column_family :d do
field :foo, :integer
end
end

class Bar < Foo
set_table_name "crazy-bars"
end
```

When I got to query Bar.first, for example, it infers the table name from "foo" and I'm left looking "foos" which is not at all what I'm after...

This is happening in 0.2.1.

Let me know if you need any additional info - this is my first GitHub issue report. Looking forward to learning how to contribute and assisting.