jpfuentes2 (at gmail)

FYI, when I last looked into this problem, the issue is that AREL doesn't think the table exists when you do a create - for some reason it does not have the oth...

Here's the new patch applied to edge (master). You are right about the 1st case, it was not working in rails 3 pre, but is working now with 3.0.0 and 3.0.1.

(on Rails 3.0.1)

To be clear on #1 the module's table_name_prefix is ignored because rails simply uses the module's name instead of the provided prefix:

module...

Including a patch to fix #2. set_table_name now accepts :prefix option like so

module Testing
  def self.table_name_prefix
    'prefix_'
  end
end

class Testi...

As far as 1 is concerned, it seems like it has something to do with autoloading models. When I do the following, the prefix is respected:

module Testing
  def ...

Update: apparently the issue is with creating records. I can issue a find for either model on both schemas:

When I put in this test.rb

p User.columns
p Post.co...

gem 'rails', '3.0.0.rc'
gem 'mysql'

When using multiple schemas in AR models, AREL throws an error whenever I try to use a schema other than the one specified i...

Using rails 3.0.0.rc

A module's table_name_prefix method is not respected in two cases:

1) vanilla - the prefix is ignored and uses pluralized module name
2) wh...