I think my patch is merited, but if nobody else thinks so then I'll
defer to the wisdom of the group. That said, the workaround provided
by bitsweat doesn't make sense to me. I wonder if perhaps I didn't get
my point across in the description.
Oh and I don't quite understand how it is pleasantly pluggable either.
Looks like a total hack to me.
Obie
On 6/29/06, Michael Koziarski <[EMAIL PROTECTED]> wrote:
I think something like this may be more suitable for acts_as_legacy.
There are a myriad of enterprise naming standards (ZX_CST_ID__) and
we'll never support them all.
On 6/28/06, Obie Fernandez <[EMAIL PROTECTED]> wrote:
> wtf? did I miss a previous discussion on this or something? That's an
> ugly hack if I've ever seen one.
>
> - obie
>
> Changes (by bitsweat):
>
> * resolution: => wontfix
> * version: => 1.1.1
> * status: new => closed
>
> Comment:
>
> Pass a block wrapping the default table name to {{{set_table_name}}}
> {{{
> class ActiveRecord::Base
> set_table_name { @squished_table_name ||= original_table_name.gsub('_',
> '') }
> end
> _______________________________________________
> Rails-core mailing list
> Rails-core@lists.rubyonrails.org
> http://lists.rubyonrails.org/mailman/listinfo/rails-core
>
--
Cheers
Koz
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
