On Jun 29, 2006, at 3:36 PM, Obie Fernandez wrote:
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.

It's not a total hack workaround, it's a feature! Passing a block to set_table_name is an ugly dog (the cache var doesn't help) but it's there so you can transform the default table name as you like. A plugin is natural considering the usage you want is uncommon and covered by the public API.

jeremy
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core

Reply via email to